dbcve.org
NessusApplication · Tenable

CVE-2024-0971

MEDIUM · 6.5 CVSS v3.1 Published 2024-02-07
Fix available
A fix is available. Upgrade to 10.7.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
A SQL injection vulnerability exists where an authenticated, low-privileged remote attacker could potentially alter scan DB content.

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

SQL injection vulnerability in scan database functionality allows an authenticated, low-privileged remote attacker to inject malicious SQL queries and potentially modify scan database content.

MitigationImplement parameterized queries or prepared statements for all database operations, apply principle of least privilege to database users, and validate/sanitize all user inputs before using them in SQL statements.

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
NessusApplication
Affected:< 10.7.0

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checks

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

  1. Confirm Tenable Nessus is installed
    Identify if Tenable Nessus is the vulnerability scanner product in use in your environment
    Affected if The product is Tenable Nessus and the version is below 10.7.0
  2. Check installed Nessus version
    Use the Nessus web interface (Help > About) or run 'nessusd -v' from the command line to determine the exact version number
    Affected if The installed version is lower than 10.7.0
  3. Verify remote authentication is enabled
    Check Nessus authentication settings in the web interface under Settings > Users or by reviewing nessusd configuration for remote user access
    Affected if Remote authentication is enabled and low-privileged users can access the scan database feature
  4. Confirm scan database feature is accessible
    Check if the scan database functionality is accessible to authenticated users, particularly low-privileged accounts
    Affected if Low-privileged authenticated users can access or interact with the scan database functionality
  5. Review database user privileges
    Examine the database user permissions configured for Nessus scanning operations
    Affected if Database users associated with scan operations lack proper privilege restrictions

You are affected if Tenable Nessus is installed with a version lower than 10.7.0 and low-privileged remote users can access the scan database functionality.

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 10.7.0 or later
Fixed in 10.7.0
Interim mitigation

Implement parameterized queries or prepared statements for all database operations, apply principle of least privilege to database users, and validate/sanitize all user inputs before using them in SQL statements.

Recommended fix Moderate confidence

Nessus 10.7.0

  1. Back up your Nessus installation, including all scan data, policies, and configurations
  2. Download Nessus version 10.7.0 from the official Tenable download portal (www.tenable.com/products/nessus/nessus-downloads)
  3. Stop the Nessus service before upgrading
  4. Install the Nessus 10.7.0 package using the appropriate installer for your operating system
  5. Start the Nessus service after installation completes
  6. Verify the upgrade was successful by logging into the Nessus web interface and confirming the version displays 10.7.0
  7. Review and re-apply any custom configurations or plugins if needed
Caveat Review Nessus 10.7.0 release notes for any configuration or plugin changes before upgrading

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

Fix this in Nessus 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-2024-0971 — 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-2024-0971 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