CVE intelligence and bounded remediation
CVE-2024-3289 — When installing Nessus to a directory outside of the default location o… security vulnerability
High
CVSS 7.8
When installing Nessus to a directory outside of the default location on a Windows host, Nessus versions prior to 10.7.3 did not enforce secure permissions for sub-directories. This could allow for local privilege escalation if users had not secured the directories in the non-default installation location.
- Severity
- High
- CVSS
- 7.8 (3.1)
- Published
- 2024-05-17
- CISA KEV
- Not currently listed
- Ecosystem
- windows/system
- Weaknesses
- CWE-281
Affected products
No browser-safe affected-product rows are available.
Matched remediation archetype
Privilege escalation and unsafe privilege management
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Map service accounts, operating-system identities, roles, capabilities, impersonation, set-user transitions, and administrative helper paths.
- Determine whether untrusted users or lower-privilege processes can reach the affected transition or modify inputs it trusts.
- Review file, socket, registry, device, job, container, and cloud-role permissions used before and after privilege changes.
Remediate safely
- Apply the supported fix and redesign privileged operations as a minimal, authenticated, allowlisted interface.
- Drop privileges before processing untrusted input, verify the drop succeeds, and remove unnecessary roles, capabilities, and write permissions.
- Validate ownership and permissions at time of use and add explicit lower-to-higher privilege boundary tests.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.