CVE-2022-4313
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 · uneditedA vulnerability was reported where through modifying the scan variables, an authenticated user in Tenable products, that has Scan Policy Configuration roles, could manipulate audit policy variables to execute arbitrary commands on credentialed scan targets.
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 confidenceAuthenticated users with Scan Policy Configuration roles can manipulate audit policy variables to achieve arbitrary command execution on credentialed scan targets. The vulnerability stems from insufficient input validation of scan variables, allowing injection of malicious commands that are then executed during credentialed scans.
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.4.2< 202212081952CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 Nessus versionIn the Nessus UI, go to About (or use the API: GET /server/properties). Compare the version to the affected range: < 10.4.2Affected if The installed version is below 10.4.2
-
Check Plugin Feed versionIn the Nessus UI, go to Plugins > Feed Settings (or use the API: GET /plugins/plugin_feed_info). Compare the feed version to 202212081952Affected if The Plugin Feed version is earlier than 202212081952
-
Identify Scan Policy Configuration role assignmentsIn Nessus, go to Users > Users and Roles. Review which users have the Scan Policy Configuration role assignedAffected if Any user account (especially untrusted or non-administrator accounts) has the Scan Policy Configuration role enabled
-
Review audit policy scan variablesExamine existing scan policies under Policies > Scan Policies. Inspect any custom audit variables, macros, or user-defined parameters for unusual syntax or command-like entriesAffected if Audit policies contain unexpected command injection patterns in variable fields (such as semicolons, backticks, or $(... ) constructs)
-
Check for credentialed scan usageReview active or historical scans in the Scans folder. Identify scans that use credentials (e.g., SSH, Windows, database credentials) for target systemsAffected if Credentialed scans exist in the environment (the vulnerability is exploited during credentialed scans)
A user is affected if their Nessus version is below 10.4.2 or Plugin Feed is before 202212081952 AND there are users with Scan Policy Configuration roles AND credentialed scans are configured.
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.4.2202212081952
Restrict Scan Policy Configuration roles to only trusted administrators, apply vendor patches when available, and implement least-privilege access controls for scan policies.
Nessus 10.4.2, Plugin Feed 202212081952
- Upgrade Nessus to version 10.4.2 or later
- Upgrade the Nessus Plugin Feed to version 202212081952 or later
- After upgrading, verify the versions by checking About Nessus in the web interface to confirm the upgrade was successful
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-4313 — 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-4313 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