[Implemented] Grouping multiple (vulnerable) programs

[OLLI_S]

What about also bundling multiple instances of the same application?

• FreeCommander XE
  • FreeCommander XE (C:\Program Files\FreeCommander XE\FreeCommander.exe)
  • FreeCommander XE (C:\Program Files\FreeCommander XE\backup\FreeCommander.exe)
  • FreeCommander XE (D:\PortableApps\PortableApps\FreeCommanderPortable\App\FreeCommanderXE\FreeCommander.exe)

And what about bundling 32-Bit and 64-Bit instances of the same application?

• Toolbox for VulnDetect
  • Toolbox for VulnDetect 32-Bit (D:\Lazarus\Toolbox for VulnDetect\Released Versions\Version 3.0\Toolbox for VulnDetect.exe)
  • Toolbox for VulnDetect 64-Bit (D:\Lazarus\Toolbox for VulnDetect\Released Versions\Version 3.0\Toolbox for VulnDetect x64.exe)

[OLLI_S]

@OLLI_S said in Grouping multiple (vulnerable) programs:

indows 10 Professional

I suggested above that you show one line for Windows and below that you should show all applications that are bundled with Windows.
You should also show the exact version number of Windows, like:

Windows 10 Professional Version 1809 (Build 17763.316)

[Tom]

@OLLI_S said in Grouping multiple (vulnerable) programs:

What about also bundling multiple instances of the same application?

• FreeCommander XE
  ....

And what about bundling 32-Bit and 64-Bit instances of the same application?
....

The rule of thumb that we will apply to bundling is the following:
If an installer installs both 32bit and 64bit versions, then we intend to bundle them.
If it requires downloading and running two different installers, then it will not be bundled.

In your example with FreeCommander, then we will bundle them, if the "backup" folder is created by the installer. If you created it manually, then we usually consider it separate installations (but manually moving exe files may class with the bundle specifications).
The PortableApps will generally not be considered bundled, but rather separate installations.

[OLLI_S]

For FreeCommander the backup folder is created automatically.
So you should bundle it (make it expandable and show the backup version as "bundled").

Here is an other specialty: FreeFileSync
I have installed FreeFileSync normally (not Portable) and I see the following files:

1. C:\Program Files\FreeFileSync\FreeFileSync.exe
2. C:\Program Files\FreeFileSync\Bin\FreeFileSync_Win32.exe
3. C:\Program Files\FreeFileSync\Bin\FreeFileSync_x64.exe
4. C:\Program Files\FreeFileSync\Bin\FreeFileSync_XP.exe

File 1. is detected by VulnDetect.
It is only 462 KB in size and is only a Launcher that starts the correct EXE file (files 2., 3. or 4.) depending on your system.
So when I start FreeFileSync.exe (launcher) then the FreeFileSync_x64.exe is started as child process.

So here you should also show FreeFileSync expandable and show all 3 platform-related files as child.
So it looks like the process tree structure.

[OLLI_S]

You also should group:

• Elite Dangerous
  • Elite Dangerous Launcher

---

• Star Citizen
  • RSI Launcher
    • 7-Zip

---

• The Dark Mod
  • The Dark Mod Updater/Downloader
  • The Dark Mod x32
  • The Dark Mod x64

The Dark Mod is not added yet, see https://vulndetect.org/topic/495/the-dark-mod-game-request
The Dark Mod Updater/Downloader is not requested yet, because the version number in the app is not correct

---

But the Launchers can be updated separately from the game.
So there can be new versions of the game available but also new versions of the launcher.
And I can update the launcher but not update the game.

[OLLI_S]

@Tom I wrote in Grouping multiple (vulnerable) programs:

But the Launchers can be updated separately from the game.
So there can be new versions of the game available but also new versions of the launcher.
And I can update the launcher but not update the game.

Do you have any idea how you will display this, when there is an update for the Launcher available but not for the game itself?
So an update for the bundled app and not for the parent applications.

[OLLI_S]

@OLLI_S said in Grouping multiple (vulnerable) programs:

how you will display this, when there is an update for the Launcher available but not for the game itself?
So an update for the bundled app and not for the parent applications.

Today I updated some apps, also the following:

• I had an update for the Elite Dangerous Launcher but not for Elite Dangerous (the game)
• I had an update for Star Citizen (the game) but not for the RSI Launcher

So you should show the user updates for bundles.

[OLLI_S]

@Tom I think we can mark this topic as "Implemented" because you added "Bundling".
If there are bundling issues then we should add new topics for each app in the detection issues.
Do you agree?

[Tom]

@OLLI_S I agree

[OLLI_S]

OK, I mark this idea as Implemented and move it to the category Implemented Feature Requests.