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

    353 Topics
    2k Posts
    OLLI_SO
    Name of the app: AppControl Developer AppControl Labs Website https://www.appcontrol.com/ Download Site: https://www.appcontrol.com/ Version number displayed in the app: 1.4.0.415 App-Icon: [image: AppControl_Icon.png] Here the information extracted from the EXE file: File name and path: C:\Program Files\AppControl\ui\AppControl.exe Product Name: AppControl Internal Name: AppControl Original Filename: AppControl.exe File Description: AppControl Company: AppControl Labs Legal Copyright: (C) 2026 AppControl Labs Legal Trademarks: Comments: File Version String: 1.4.0+415 File Version: 1.4.0.415 Product Version String: 1.4.0+415 Product Version: 1.4.0.415
  • Post requests for apps that you wish to see updated automatically

    25 Topics
    40 Posts
    T
    Why we only patch the two most recent major Python versions Python follows a lifecycle where only the newest major versions receive full support, including official binary installers. Once a version moves into security-fix-only mode, upstream stops shipping these installers. From Python 3.12 release notes: “Python 3.12 is now in the ‘security fixes only’ stage… releases of those are made irregularly in source-only form... binary installers are no longer provided.” Source: https://www.python.org/downloads/release/python-31213/ For older versions: Updates are source-only, not packaged installers No consistent or supported upgrade path on Windows Effectively shifts maintenance to manual builds or downstream distributions Bottom line: If upstream doesn’t ship a proper installer, we don’t have a reliable or safe way to patch it.
  • Announcements regarding the VulnDetect project

    62 Topics
    61 Posts
    A
    Autodesk products can be deployed using VulnDetect Custom Software or PatchPro Advanced Customization. This guide covers both the initial installation and future patching of Autodesk products. 1. Acquire the Installation Files Download the required installer from the Autodesk website or your organization’s Autodesk Account. The download method varies between products: Licensed products such as AutoCAD, AutoCAD LT, and Revit normally require access to an Autodesk Account with the appropriate subscription. DWG TrueView is free and can be downloaded directly from Autodesk. Autodesk may use different download and extraction methods depending on the product. After downloading or extracting the Autodesk installer, you should have a folder containing all the installation files. Compress the complete installer folder into a single .zip or .7z archive. Do not remove files or change the internal folder structure. For a full installation, you need: The Autodesk .zip or .7z installer package. The universal Autodesk deployment script linked below. Universal Autodesk deployment script: https://stream.vulndetect.com/e/Deploy-AutodeskProduct.ps1 Deploy-AutodeskProduct.ps1 Note: This PowerShell script is provided as an example to assist with Autodesk deployments. It is not digitally signed and is not part of SecTeer's officially supported package library. We recommend testing it in your environment before deploying it broadly. SHA-256: 1d51b8efad215ae69a23c88208188867cf4e710f702ec35c65ef1f9eee95f1d4 The script automatically extracts the archive, locates the Autodesk installer, runs it silently, and verifies the installation. Important: Only include one Autodesk .zip or .7z package in each deployment. 2. Build the Deployment Configuration -VulnDetect Custom Software Create a new Custom Software configuration and give it a fitting name, for example: Autodesk AutoCAD 2027 – English x64 Configure the deployment as follows: Installation context: System Main file: Deploy-AutodeskProduct.ps1 Additional file: The Autodesk .zip or .7z package Installer command: The installer command should look like the example below. Remove any arguments from the Custom Installer Arguments field. powershell.exe -NoLogo -NonInteractive -ExecutionPolicy Bypass -File .\Deploy-AutodeskProduct.ps1 The name of the Autodesk archive does not matter. The script automatically finds the included archive. -PatchPro Advanced Customization Locate Autodesk product in question under Available Applications and select it. Open Customize and add: Main file: Deploy-AutodeskProduct.ps1 Additional file: The Autodesk .zip or .7z package Installer command: The installer command should look like the example below. Remove any arguments from the Custom Installer Arguments field. powershell.exe -NoLogo -NonInteractive -ExecutionPolicy Bypass -File .\Deploy-AutodeskProduct.ps1 Publish the application and assign it in Intune. Best practice is to test it on one or two devices before committing to a large-scale deployment. 3. Patch Autodesk Products Most Autodesk products publish updates as an update.exe file. These updates can normally be deployed without the PowerShell script. VulnDetect Prepare and approve the update as follows: Download the correct update.exe for the product, version, architecture, and language. Locate the relevant Autodesk application under Approvals in VulnDetect. Enable Customization using Custom Tag Approval. Add update.exe as the main file. Make sure the installation command is: update.exe -q Review the configuration and approve the update. PatchPro Prepare and publish the update as follows: Download the correct update.exe for the product, version, architecture, and language. Locate the relevant Autodesk application under Available Applications in PatchPro. Select Custom Publish. Add update.exe as the main file. Make sure the installation command includes the -q argument: update.exe -q If you also have a configuration for deploying the full application, add (Update) to the name of the update configuration. This makes it easier to distinguish between the deployment and update configurations. Review the configuration and publish the update. Important: DWG TrueView Patching DWG TrueView is handled differently. Autodesk does not normally provide DWG TrueView updates as a separate update.exe package. Instead, the latest complete installer must be deployed. To update DWG TrueView: Download the latest complete DWG TrueView .zip or .7z installer. Add Deploy-AutodeskProduct.ps1 as the main file. Add the new DWG TrueView installer archive as the additional file. Use the following installation command: powershell.exe -NoLogo -NonInteractive -ExecutionPolicy Bypass -File .\Deploy-AutodeskProduct.ps1 The script detects the existing DWG TrueView installation, removes the older version when necessary, and installs the newer full release.
  • Detection errors and issues should be posted here

    482 Topics
    2k Posts
    OLLI_SO
    For Notepad++ VulnDetect detects the version 8.9.8.1. But VulnDetect recommends the version 8.9.8 (VulnDetect recommends an OLDER version). Please recommend the currently available version! Here the information extracted from the EXE file: File name and path: C:\PortableApps\PortableApps\_Notepad++\notepad++.exe Product Name: Notepad++ Internal Name: notepad++.exe Original Filename: notepad++.exe File Description: Notepad++ Company: Don HO don.h@free.fr Legal Copyright: Copyleft 1998-2023 by Don HO Legal Trademarks: Comments: File Version String: 8.9.8.1 File Version: 8.9.8.1 Product Version String: 8.9.8.1 Product Version: 8.9.8.1
  • Detection errors and issues should be posted here

    49 Topics
    157 Posts
    G
    Hi, Git has an embedded curl wich is not detected as embedded. [image: image.jpeg] Hope this helps. Regards.
  • This category will be used to keep track of user contributed suggestions

    143 Topics
    474 Posts
    T
    @GregAlexandre Where exactly do you see an issue with IPv6? As far as I know, then we support IPv6 everywhere in Production, and approx. 13-15% of all client traffic is IPv6 based.
  • This category will be used to keep track of bugs reported by users

    50 Topics
    288 Posts
    OLLI_SO
    I recognized, that for the Sysinternals Tools, there is the installed version missing, when I expand the bundled applications: [image: affa92de-2a06-4f5a-bdbe-dbc310b2f5a5-image.jpeg] This information should be displayed!
  • Feel free to discuss what was good or bad in Secunia PSI and what you expect from VulnDetect

    19 Topics
    70 Posts
    T
    The reported Notepad++ supply-chain incident, as described in public reporting, was limited to the application’s built-in auto-update mechanism. SecTeer VulnDetect does not use or depend on the Notepad++ auto-updater. All Notepad++ packages distributed through SecTeer are downloaded directly from the official vendor source and processed through SecTeer’s own validation pipeline. This includes: Verification of the Authenticode signature where the vendor provides signed binaries Malware scanning using Microsoft Defender Additional reputation-based checks as a supplementary control SecTeer packages are released independently of the vendor’s auto-update channel and are not delivered through the update mechanism involved in the reported incident. As a result, SecTeer did not distribute compromised code, and SecTeer’s distribution infrastructure was not impacted. A system could only have received the compromised update if the built-in Notepad++ auto-update feature was enabled on the system In short: SecTeer’s update mechanism was not involved in the incident, and no compromised Notepad++ packages were delivered through the SecTeer platform.