dbcve.org
Tenable.scApplication · Tenable

CVE-2022-0130

HIGH · 8.1 CVSS v3.1 Published 2022-01-14
Fix available
A fix is available. Upgrade to after 5.19.1 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Tenable.sc versions 5.14.0 through 5.19.1 were found to contain a remote code execution vulnerability which could allow a remote, unauthenticated attacker to execute code under special circumstances. An attacker would first have to stage a specific file type in the web server root of the Tenable.sc host prior to remote exploitation.

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 confidence

Tenable.sc versions 5.14.0 through 5.19.1 contain a pre-authentication remote code execution vulnerability. An unauthenticated remote attacker can achieve RCE by first staging a specific file type in the web server root of the Tenable.sc host, which is then leveraged during exploitation.

MitigationUpgrade Tenable.sc to version 5.19.2 or later. Additionally, restrict write access to the web server root directory to prevent attackers from staging the required file, and monitor for suspicious files in that location.

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
Tenable.scApplication
Affected:>= 5.14.0, <= 5.19.1

CVSS 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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Tenable.sc version
    Locate and read the Tenable.sc version information from the application interface or system configuration files. This is typically visible in the product UI header or accessible via API at the /rest/system endpoint.
    Affected if The installed version falls within the range 5.14.0 through 5.19.1 inclusive.
  2. Locate the web server root directory
    Determine the document root path used by the Tenable.sc web server. This is typically found in the web server configuration (such as httpd.conf for Apache or nginx.conf).
    Affected if You are unable to locate or access the web server root configuration.
  3. Verify web server root write permissions
    Inspect file system permissions on the identified web server root directory to determine if unprivileged users or processes can write files to this location.
    Affected if The web server root directory has world-writable permissions or permissions that allow unauthenticated attackers to create files.
  4. Inspect web server root for suspicious files
    List all files in the web server root directory and examine them for unexpected or unrecognized file types, especially those that could be used as staging payloads for exploitation.
    Affected if Unexpected files exist in the web server root, particularly file types not deployed as part of normal Tenable.sc operation.

A user is affected if Tenable.sc version 5.14.0 through 5.19.1 is installed AND the web server root directory permits write access from unauthenticated attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 5.19.1
Interim mitigation

Upgrade Tenable.sc to version 5.19.2 or later. Additionally, restrict write access to the web server root directory to prevent attackers from staging the required file, and monitor for suspicious files in that location.

Recommended fix Moderate confidence

Tenable.sc 5.19.2 or later (any version higher than 5.19.1)

  1. 1. Back up the Tenable.sc current installation and configuration
  2. 2. Review Tenable.sc release notes at www.tenable.com for version 5.19.2 or later
  3. 3. Download the latest stable Tenable.sc release (version 5.19.2 or higher)
  4. 4. Follow Tenable's upgrade documentation to install the new version
  5. 5. Verify the upgrade was successful and the web interface is accessible
  6. 6. Test that core scanning functionality works as expected
Caveat Review release notes for this specific version jump as there may be database migrations or dependency changes; test in a staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tenable.sc Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-0130 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-0130 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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