Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2024-3292 Overview
CVE-2024-3292 is a race condition vulnerability affecting the Tenable Nessus Agent on Windows hosts. An authenticated local attacker can modify installation parameters during the install process, resulting in arbitrary code execution on the Nessus host. The flaw is classified as a Time-of-Check Time-of-Use (TOCTOU) issue under CWE-367. Successful exploitation produces a scope change, impacting confidentiality, integrity, and availability beyond the vulnerable component.
Critical Impact
A local authenticated user can race the installer to inject malicious parameters and execute arbitrary code with the elevated privileges of the Nessus Agent installation context.
Affected Products
- Tenable Nessus Agent for Windows (versions prior to the fix referenced in Tenable advisory TNS-2024-09)
- Windows hosts running vulnerable Nessus Agent installers
- Environments deploying Nessus Agent via unattended or scripted installation
Discovery Timeline
- 2024-05-17 - CVE-2024-3292 published to the National Vulnerability Database
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2024-3292
Vulnerability Analysis
The vulnerability is a Time-of-Check Time-of-Use (TOCTOU) race condition in the Windows installation routine of the Nessus Agent. During installation, parameters are validated at one point in time and consumed at another. An attacker with local authenticated access to the host can modify those parameters in the interval between validation and use.
Because the installer executes with elevated privileges, parameter tampering translates into arbitrary code execution in a higher-privileged context. The flaw requires user interaction, meaning the install must be initiated by a legitimate operator or deployment system. Once triggered, the attacker gains execution outside the original security scope of the installer process.
Root Cause
The root cause is non-atomic handling of installation inputs. The installer reads or verifies parameters, then later references the same resources without ensuring they remained unchanged. This classic TOCTOU pattern [CWE-367] allows a concurrent local process to substitute attacker-controlled content between the check and the use.
Attack Vector
Exploitation requires local access and valid credentials on the Windows host, plus a concurrent installation event. The attacker races the installer by modifying files, registry entries, or command-line inputs that the installer trusts after an initial validation step. See the Tenable Security Advisory TNS-2024-09 for vendor technical details.
No public proof-of-concept exploit is available, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog.
Detection Methods for CVE-2024-3292
Indicators of Compromise
- Unexpected child processes spawned by the Nessus Agent installer (nessus-agent-*.msi or related executables) during install windows
- Modification of installer-related files or directories by non-installer processes during active installation
- Creation of new services, scheduled tasks, or persistence artifacts coinciding with Nessus Agent install events
Detection Strategies
- Monitor Windows Installer (MSI) activity for anomalous file writes or process creation chains originating from the Nessus Agent installer
- Alert on local user processes writing to installer staging paths while an elevated installer is active
- Correlate Sysmon Event ID 1 (process create) and Event ID 11 (file create) around Nessus Agent install timestamps
Monitoring Recommendations
- Audit Nessus Agent deployment events across Windows endpoints and verify installer integrity post-install
- Review Windows Event Logs for MsiInstaller entries and unusual elevation events during agent rollout
- Baseline normal install behavior so that concurrent file or parameter modifications stand out
How to Mitigate CVE-2024-3292
Immediate Actions Required
- Upgrade the Nessus Agent for Windows to the fixed version referenced in Tenable advisory TNS-2024-09
- Restrict local login and interactive access on hosts receiving Nessus Agent installations to trusted administrators only
- Perform agent installation from protected locations where non-administrative users cannot write
Patch Information
Tenable addressed CVE-2024-3292 in the Nessus Agent release documented in TNS-2024-09. Administrators should consult the advisory for the exact fixed version and apply it to all Windows endpoints running the agent. Reinstallation should occur from a trusted staging path under administrator control.
Workarounds
- Limit the number of users with local logon rights on hosts targeted for Nessus Agent installation
- Stage installer binaries in directories with access control lists that block modification by standard users
- Avoid running the installer on multi-user systems while non-administrators are logged in interactively
# Configuration example
# Restrict write access to the installer staging directory on Windows
icacls "C:\Deploy\NessusAgent" /inheritance:r
icacls "C:\Deploy\NessusAgent" /grant:r "Administrators:(OI)(CI)F" "SYSTEM:(OI)(CI)F"
icacls "C:\Deploy\NessusAgent" /remove "Users" "Authenticated Users"
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

