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

    351 Topics
    2k Posts
    OLLI_SO
    Meantime, Synergy version 3.5.0 was released: [image: 1767004405261-13e7d0d8-a397-4708-b32b-a1105a6cbfb9-image.png] Here the information extracted from the EXE file: File name and path: C:\Program Files\Synergy\Synergy.exe Product Name: Synergy Internal Name: Synergy Original Filename: File Description: Use the keyboard, mouse, or trackpad of one computer to control nearby computers. Company: Symless Legal Copyright: Copyright © 2025 Symless Legal Trademarks: Comments: File Version String: 3.5.0 File Version: 3.5.0.0 Product Version String: 3.5.0.0 Product Version: 3.5.0.0

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

    23 Topics
    38 Posts
    T
    The release notes are out: https://www.adobe.com/devnet-docs/acrobatetk/tools/ReleaseNotesDC/continuous/dccontinuoussept2025qfe.html#dccontinuoussepttwentytwentyfiveqfe This is the official fix for the printing issue: 4529876: Data loss in printing PDF on Reader and Acrobat The packages for Acrobat/Reader in VulnDetect and PatchPro was released earlier this morning.

  • Announcements regarding the VulnDetect project

    56 Topics
    56 Posts
    A
    Advanced customization: TeamViewer install + assignment (PatchPro / VulnDetect) This approach is for customers who want to run a PowerShell script as the installer (instead of running the MSI/EXE directly). The script installs TeamViewer from an MSI placed in the same working directory and then runs a TeamViewer assignment command. Important: the PowerShell script MUST be the primary installer. The MSI must be included as an additional file. PatchPro Instructions 1. Create a new text document containing the script below. 2. Save the file as a PowerShell script (.ps1), e.g.: TVInstallAndAssign.ps1 3. Navigate to Available Applications and select TeamViewer 15 (x64) (MSI). 4. Click Custom Publish. 5. Click the downward arrow next to the Browse icon to move the TeamViewer installer into Additional Files. 6. Click the Browse icon and select your .ps1 script. 7. Remove any custom installer arguments like /qn /norestart (the script handles msiexec arguments). 8. Give the deployment a name and click Publish. [image: 1769161190965-pp-publish-tv-custom-resized.png] VulnDetect - Advanced Customization Instructions This method uses a PowerShell script as the installer. The script installs TeamViewer from an MSI placed in the working directory and then performs the assignment. The PowerShell script must be the installer. If it is not moved into the installer position, it will not execute. 1. Create a new text document containing the script below. 2. Save the file as a PowerShell script (.ps1), for example: TVInstallAndAssign.ps1 3. Navigate to Approvals and edit the desired Tag Approval. 4. Move the TeamViewer installer down using the blue arrow button. 5. Click Choose File and select your .ps1 script (this must be the installer). 6. Remove any installer arguments (these are handled by the PowerShell script). 7. Click Save. [image: 1769161203694-vd-approvals-tv-custom-resized.png] Prerequisites (read this) • The script expects the TeamViewer MSI to be included as an Additional File in the same working directory as the script. • MSI exit code 3010 is treated as success (reboot required) and will be returned as the script exit code. • The script fails if assignment does not complete successfully (non-zero exit code or timeout). • Replace the assignment id/token placeholder before publishing. Note: The assignment method varies depending on license type, this is just an example for a specific license type. # # ========================================== # SecTeer: TeamViewer Install (MSI) + Assignment # ========================================== $ScriptDir = Split-Path -Parent $MyInvocation.MyCommand.Path $LogFolder = "C:\Windows\Logs\SecTeer" $LogFile = Join-Path $LogFolder "TeamViewer-assign.log" # --- Ensure log folder exists --- if (-not (Test-Path $LogFolder)) { New-Item -Path $LogFolder -ItemType Directory -Force | Out-Null } function Write-Log { param([string]$Message) "[$(Get-Date -Format 'yyyy-MM-dd HH:mm:ss')] $Message" | Out-File -FilePath $LogFile -Append -Encoding UTF8 } Write-Log "Script started" # --- CONFIG: assignment token (MUST be replaced before deployment) --- $AssignmentArgs = 'assignment --id REPLACE_WITH_REAL_ASSIGNMENT_TOKEN' # Fail fast if placeholder still present if ($AssignmentArgs -match 'REPLACE_WITH_REAL_ASSIGNMENT_TOKEN') { Write-Log "ERROR: Assignment token placeholder not replaced. Aborting." exit 1 } # --- Locate MSI next to this script (supports .msi and .msi.msi) --- $MsiMatches = Get-ChildItem -Path $ScriptDir -File | Where-Object { $_.Name -match '^TeamViewer.*\.msi(\.msi)?$' } if (-not $MsiMatches -or $MsiMatches.Count -eq 0) { Write-Log "ERROR: No TeamViewer MSI found in $ScriptDir" Get-ChildItem -Path $ScriptDir -File | ForEach-Object { Write-Log "Found file: $($_.Name)" } exit 1 } if ($MsiMatches.Count -gt 1) { Write-Log "ERROR: Multiple TeamViewer MSI files found:" $MsiMatches | ForEach-Object { Write-Log " - $($_.FullName)" } exit 1 } $MsiPath = $MsiMatches[0].FullName Write-Log "Using MSI: $MsiPath" # --- Install TeamViewer --- Write-Log "Starting TeamViewer MSI installation" $msiArgs = "/i `"$MsiPath`" /qn /norestart" $msiProc = Start-Process -FilePath "$env:WINDIR\System32\msiexec.exe" ` -ArgumentList $msiArgs ` -Wait ` -NoNewWindow ` -PassThru $msiCode = [int]$msiProc.ExitCode Write-Log "MSI exited with code: $msiCode" # Accept 0 (success) and 3010 (success, reboot required) if ($msiCode -ne 0 -and $msiCode -ne 3010) { Write-Log "ERROR: MSI installation failed" exit $msiCode } # --- Allow post-install finalization --- Start-Sleep -Seconds 10 # --- Locate TeamViewer executable --- $TvExeCandidates = @( "C:\Program Files\TeamViewer\TeamViewer.exe", "C:\Program Files (x86)\TeamViewer\TeamViewer.exe" ) $TvExe = $TvExeCandidates | Where-Object { Test-Path $_ } | Select-Object -First 1 if (-not $TvExe) { Write-Log "ERROR: TeamViewer executable not found" $TvExeCandidates | ForEach-Object { Write-Log "Checked: $_" } exit 1 } Write-Log "Using TeamViewer executable: $TvExe" # --- Assignment --- Write-Log "Starting TeamViewer assignment" Write-Log "Executing: `"$TvExe`" $AssignmentArgs" $tvProc = Start-Process -FilePath $TvExe ` -ArgumentList $AssignmentArgs ` -PassThru ` -NoNewWindow $TimeoutMs = 120000 if (-not $tvProc.WaitForExit($TimeoutMs)) { Write-Log "ERROR: Assignment timed out after $([int]($TimeoutMs/1000)) seconds" try { $tvProc.Kill() } catch {} exit 1 } $tvCode = [int]$tvProc.ExitCode Write-Log "Assignment exited with code: $tvCode" if ($tvCode -ne 0) { Write-Log "ERROR: TeamViewer assignment failed" exit $tvCode } Write-Log "TeamViewer installation and assignment completed successfully" # Per requirement: propagate installer exit code exit $msiCode

  • Detection errors and issues should be posted here

    451 Topics
    2k Posts
    G
    @OLLI_S -> solved 3.0.23 is now the official version

  • Detection errors and issues should be posted here

    45 Topics
    149 Posts
    G
    @Tom : Nvidia app and its former (unsafe) versions are now reported in one bundle. Unsafe 7zip version which is bundled with this soft is still not reported with Nvidia app bundle but separately.

  • 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

    48 Topics
    284 Posts
    OLLI_SO
    @GregAlexandre OK, then I mark this issue as solved.

  • 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.