CVE-2022-33757
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 authenticated attacker could read Nessus Debug Log file attachments from the web UI without having the correct privileges to do so. This may lead to the disclosure of information on the scan target and/or the Nessus scan to unauthorized parties able to reach the Nessus instance.
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 · high confidenceThis is an Insecure Direct Object Reference (IDOR) vulnerability in the Nessus web UI where an authenticated attacker with standard user privileges can access debug log file attachments that should be restricted to higher-privileged users. The debug logs may contain sensitive information about scan targets and scan configurations, leading to information disclosure.
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< 10.2.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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Identify the installed Nessus versionAccess the Nessus web UI and navigate to the About or Settings page to view the version number, or use the command line to query the Nessus service versionAffected if The installed version is below 10.2.0
-
Verify standard user access to debug log endpointsLog in to the Nessus web UI with a standard (non-admin) user account and attempt to access debug log file attachment URLs or endpoints that are typically restricted to administratorsAffected if A standard user can successfully retrieve or download debug log files that should be restricted to administrator privileges
-
Inspect debug log contents for sensitive dataIf debug logs are accessible, examine the file contents to confirm they contain sensitive information such as scan targets, credentials, or configuration detailsAffected if Debug log files accessible to standard users contain sensitive scan target information or configuration data
-
Review access control configurationCheck the Nessus user role permissions and access control settings to confirm whether standard users should have restricted access to administrative functionsAffected if Standard users have been granted or inadvertently retain access to administrative debug log features
A user is affected if their Nessus installation is version 10.1.x or earlier AND standard non-privileged users can access debug log file attachments through the web UI.
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.
dbcve · scoped10.2.0
Apply the vendor patch from Tenable for this vulnerability. Until patched, implement strict access controls on the Nessus web UI and monitor for unauthorized access to debug log endpoints.
Nessus 10.2.0 or later
- Log in to the Nessus web UI as an administrator
- Navigate to the 'About' or 'Settings' page to check current version
- If version is below 10.2.0, download Nessus 10.2.0 or later from the Tenable downloads page
- Back up the Nessus configuration and scan data following standard backup procedures
- Stop the Nessus service
- Install the Nessus 10.2.0+ upgrade package
- Start the Nessus service
- Verify the upgrade was successful by checking the version in the web UI
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33757 — 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-2022-33757 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