Categories

  • Announcements regarding the VulnDetect project

    14 Topics
    123 Posts
    T
    Version 3.4.0.0 is the latest Stable release. It can be downloaded from here: https://vulndetect.com/dl/agents/secteerSetup-3.4.0.0.exe https://vulndetect.com/dl/agents/secteerSetup-3.4.0.0.msi

  • Post requests for apps that are missing

    349 Topics
    2k Posts
    OLLI_SO
    @amu and @Tom When will this app be added to your database? Please add it, this wouold really be cool! Thank you!

  • Post requests for apps that you wish to see updated automatically

    22 Topics
    35 Posts
    OLLI_SO
    Please add Keeper Password Manager to the Auto-Patching process, so it is automatically updated (when I select it). I post one app in one topic, so we can keep the topics smaller. For Keeper Password Manager there is a Choko package available: https://community.chocolatey.org/packages/keeper

  • Announcements regarding the VulnDetect project

    45 Topics
    45 Posts
    rnzR
    Hi, Due to Zoom phasing out support for Windows 32-bit by December 2025, all upgrades for 64-bit OS's will be done using the 64-bit installer. For more details, please refer to the official vendor announcement: https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0079569

  • Detection errors and issues should be posted here

    430 Topics
    2k Posts
    OLLI_SO
    @amu PureSync was updated to Version 8.0.2 Build 7496: [image: 1748517318059-334460ff-b70e-4c1a-badf-fbdb6c3238ad-image.png] VulnDetect shows the installed version 8.00.7499 and recommends 8.0.0 Build 7143: [image: 1748517611451-8ae0a76c-237e-4eb5-971e-7eae8aabaefc-image.png] Here the information extracted from PureSync.exe: File name and path: C:\Program Files (x86)\Jumping Bytes\PureSync\PureSync.exe Product Name: PureSync Internal Name: PureSync Original Filename: PureSync.exe File Description: PureSync, a file and folder synchronization and backup tool, by Jumping Bytes Company: Jumping Bytes Legal Copyright: Jumping Bytes, Christoph Guentner, (c) 2025 Legal Trademarks: Comments: File Version String: 8.00.7496 File Version: 8.0.0.7496 Product Version String: 8.00.7496 Product Version: 8.0.0.7496 Here the information extracted from PureSync.dll: File name and path: C:\Program Files (x86)\Jumping Bytes\PureSync\PureSync.dll Product Name: PureSync Internal Name: PureSync Original Filename: PureSync.dll File Description: PureSync Company: Jumping Bytes Legal Copyright: Jumping Bytes, Christoph Guentner, (c) 2025 Legal Trademarks: Comments: File Version String: 8.00.7499 File Version: 8.0.0.7499 Product Version String: 8.00.7499 Product Version: 8.0.0.7499 Unfortunately, the correct version number is neither shown in the PureSync.exe, nor in the PureSync.dll. In the PureSync.exe you have at least the correct Build Number 7496. So you have to add here - again - a special rule, that shows 8.0.2 Build 7496 when the version in the PureSync.exe is 8.00.7496. I will also tell this - again - to the programmer of PureSync, where I am in personal contact with.

  • Detection errors and issues should be posted here

    45 Topics
    148 Posts
    G
    Hi, Two instances of Python embedded with Gimp are seen after installing GIMP 3.0.x [image: 1747603841742-2e631897-73d7-45ca-acef-79b81caf5e81-image.png] Hope this helps. Regards.

  • This category will be used to keep track of user contributed suggestions

    143 Topics
    472 Posts
    OLLI_SO
    I am using the CSV export on a daily base, it is really very useful. But sone things should really be improved. Recommended Version For some tools (like “MiTeC Icon Explorer") the recommended version (5.2.0) is older, than the installed version (5.3.0). In the list of applications you do not show a recommended version. In my CSV export I have 15 applications, where the recommended version is different, but only for 3 entries the recommended version is newer. Therefore, the recommended version should not be exported, when it is older or equal to the installed version. Export Tool Collections All tools from "Sysinternals" are bundled as "Sysinternals Suite". The whole suite including all apps is not exported. You should export the package headline ("Sysinternals Suite") and also all included tools. I do not know if it causes trouble when the package headline ("Sysinternals Suite") has an empty column "File". Identical naming for Apps in Tool Collections All tools from Sysinternals begin with the text "Sysinternals" (like "Sysinternals DebugView" or "Sysinternals Process Explorer") what is great, when you sort the exported CSV. Also all tools from MiTeC begin with the text "MiTeC". But only some tools from NirSoft begin with the text "NirSoft" and none of the tools from Nenad Hrg begin with "Nenad Hrg". Export status "Patch" and "Update" In the UAT instance you show the status "Patch" and "Update". This status is not yet exported, but it is really very helpful! Please consider these suggestions for the CSV export.

  • This category will be used to keep track of bugs reported by users

    47 Topics
    278 Posts
    G
    This issue is fixed for quite a long time.

  • Feel free to discuss what was good or bad in Secunia PSI and what you expect from VulnDetect

    18 Topics
    70 Posts
    T
    During testing of the Google Chrome 131.0.6778.109 MSI package, we found that it was broken, resulting in Exit Code 1603 after attempting to spawn a UAC prompt as the SYSTEM user. This issue occurs both when upgrading via VulnDetect and Intune. In some cases, it even breaks the existing installation during rollback of the failed update. As a result, we pulled the update before releasing it to customers. Once Google has fixed the Enterprise "ready" MSI installer, we will update the package and make it available after thorough testing. Please "upvote" the following post by Mikhail Gurin if you are affected by this and have a Google account. Hopefully, this will help make Google prioritize the fix: https://support.google.com/chrome/thread/311347547 For reference, we use the following installers: https://dl.google.com/tag/s/dl/chrome/install/googlechromestandaloneenterprise.msi https://dl.google.com/tag/s/dl/chrome/install/googlechromestandaloneenterprise64.msi We also tested the EXE-based installers for offline deployment but found that these are incompatible with MSI-based installations. It should be noted that the MSI works if launched interactively as a regular user who can approve the UAC prompt.