CVE-2024-5759
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn improper privilege management vulnerability exists in Tenable Security Center where an authenticated, remote attacker could view unauthorized objects and launch scans without having the required privileges
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is an improper privilege management vulnerability in Tenable Security Center where authenticated users can bypass authorization checks to view objects and launch scans they are not permitted to access. The flaw allows privilege escalation through the application's role-based access control (RBAC) mechanism.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 6.3.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Tenable Security Center versionLog into the Security Center web interface and navigate to System > About, or run 'nessusd -v' via command line to determine the installed version numberAffected if The installed version is 6.3.0 or lower (any version <= 6.3.0)
-
Verify RBAC is configuredNavigate to Users > Roles in the Security Center interface to confirm role-based access control is enabled and users are assigned to custom or built-in rolesAffected if RBAC is actively configured with multiple user roles defined
-
Review audit logs for unauthorized scan launchesNavigate to System > Logs > Audit and filter for scan-related events. Look for scan execution events where the user initiating the scan should not have permission based on their assigned roleAffected if Audit logs show scans launched by users who lack explicit permission to those repositories or scan zones
-
Check for unauthorized object accessReview the Activity > Events log and compare object/repository access against each user's assigned role. Look for access to repositories, assets, or dashboards outside the user's defined role permissionsAffected if Users accessed repositories, assets, or sensitive objects not assigned to their role
-
Audit user role assignments for privilege escalation pathsNavigate to Users > Users and cross-reference each user's assigned role against the repositories and scan zones they can access. Identify any mismatches between role permissions and actual accessible resourcesAffected if Users can access resources beyond what their assigned role should permit
If running Tenable Security Center version 6.3.0 or lower with RBAC enabled, and audit logs or role audits reveal users accessing resources outside their assigned permissions, the environment is affected by this privilege escalation vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor patch from Tenable when available. In the interim, audit user role assignments, enable detailed audit logging, and monitor for unauthorized scan execution or access to sensitive objects.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5759 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-5759 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data