[Solved] Left Overs in WSCC
-
I am using WSCC and here there are some older applications, which are "left overs" (older versions).
I have Rufus Version 4.3 ( Build 2090) in the folder:
C:\Users\olive\OneDrive\PortableApps\PortableApps\_WSCCPortable\Other Utilities\rufus-p.exe
WSCC updated Rufus to version 4.4 (Build 42103), but WSCC stored the EXE in the "x64" sub-folder:
C:\Users\olive\OneDrive\PortableApps\PortableApps\_WSCCPortable\Other Utilities\x64\rufus-p.exe
WSCC did not delete the old version of Rufus, so I have it now twice on my PC.
When I start WSCC in a Sandbox* then only the x64 version is downloaded.
WSCC also delivers SumatraPDF and here WSCC also keeps older versions:
SumatraPDF.exe (Version 3.5.2.0) SumatraPDF-3.4.2-32.exe (Version 3.4.2.0) SumatraPDF-3.4.1-32.exe (Version 3.4.1.0) SumatraPDF-3.3.3-32.exe (Version 3.3.3.0)
When I start WSCC in a Sandbox, I only have the newest version is downloaded.
When I start the older versions (the EXE files with the version number in the file name) in my Sandbox, then SumatraPDF opens (these files are also portable versions and not installers).
In VulnDetect (Personal UI) Rufus and SumatraPDF are bundled with WSCC.
But here I do only see the current version of SumatraPDF.@Tom you should:
- Show all versions of SumatraPDF
- Mark the older versions of SumatraPDF as Outdated
- Mark the older version of Rufus as Outdated
-
@OLLI_S From what I can see, then detection of Rufus and SumatraPDf is working as expected. As you know, part of our detection relies on the original filenames, so when an app or user renames EXE files, it easily (and intentionally) bypasses our detection.
-
OK, then I mark this issue as solved.
-