dbcve.org
Identity ExposureApplication · Tenable

CVE-2024-3232

MEDIUM · 6.8 CVSS v3.1 Published 2024-07-16
Fix available
A fix is available. Upgrade to 3.59.4 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable

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 formula injection vulnerability exists in Tenable Identity Exposure where an authenticated remote attacker with administrative privileges could manipulate application form fields in order to trick another administrator into executing CSV payloads. - CVE-2024-3232

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

A formula injection vulnerability in Tenable Identity Exposure allows an authenticated administrator to inject malicious formulas into application form fields. When data is exported to CSV format and opened in spreadsheet software, these formulas (prefixed with =, +, -, @, or tab) can execute arbitrary commands on the victim's system.

MitigationImplement output encoding/sanitization of formula characters (=, +, -, @, tab, carriage return) in all data fields before CSV export. Alternatively, prepend a single quote (') to fields starting with formula characters or use a safer export format.

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
Identity ExposureApplication
Affected:< 3.59.4

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/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. Confirm Tenable Identity Exposure is deployed
    Identify whether Tenable Identity Exposure (formerly Tenable.io Identity and Access or similar naming) is installed in your environment, either as a hosted service or on-premise deployment
    Affected if The product is present in your environment
  2. Locate the installed version
    Access the Tenable Identity Exposure administrative interface, typically via the web console, and navigate to the settings or about section to find the current version number
    Affected if You can confirm the exact version from the interface
  3. Compare version against affected range
    Check if the installed version is lower than 3.59.4 by comparing the version string you found
    Affected if Version is less than 3.59.4
  4. Verify CSV export functionality exists
    Log in as an administrator and determine if the application includes any feature that exports data to CSV format, such as reports, data dumps, or user exports
    Affected if CSV export capability is available in the application

You are affected if Tenable Identity Exposure is installed at a version lower than 3.59.4 and the CSV export feature is accessible to authenticated administrators.

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

Implement output encoding/sanitization of formula characters (=, +, -, @, tab, carriage return) in all data fields before CSV export. Alternatively, prepend a single quote (') to fields starting with formula characters or use a safer export format.

Recommended fix High confidence

Tenable Identity Exposure 3.59.4

  1. 1. Back up the current Tenable Identity Exposure configuration and database according to Tenable documentation.
  2. 2. Consult Tenable Identity Exposure release notes for version 3.59.4 to verify compatibility with your current environment.
  3. 3. Download Tenable Identity Exposure version 3.59.4 or later from the official Tenable downloads portal.
  4. 4. Follow Tenable's standard upgrade procedure for Identity Exposure, ensuring services are properly stopped before upgrade.
  5. 5. After upgrade, verify the application is functioning correctly and the version shows 3.59.4 or later.
  6. 6. Confirm the formula injection vulnerability is resolved by testing CSV export functionality if applicable.

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

Fix this in Identity Exposure Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-3232 — 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-3232 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