CVE-2024-31980
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 has been identified in Parasolid V35.1 (All versions < V35.1.256), Parasolid V36.0 (All versions < V36.0.210), Parasolid V36.1 (All versions < V36.1.185). The affected application contains an out of bounds write past the end of an allocated buffer while parsing a specially crafted X_T part file. This could allow an attacker to execute code in the context of the current process. (ZDI-CAN-23468)
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 confidenceParasolid contains an out-of-bounds write vulnerability when parsing X_T part files. The parsing logic writes past the end of an allocated buffer, allowing an attacker to execute code in the context of the current process by tricking a user into opening a specially crafted malicious X_T file.
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>= 35.1, < 35.1.256>= 36.0, < 36.0.210>= 36.1, < 36.1.185CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Parasolid versionLocate the Parasolid component within your Siemens product (such as NX, Teamcenter, or standalone Parasolid) and retrieve the version information. This is typically found in the product's About dialog, in installation directories, or via the host application's version information panel. The version is usually displayed as V35.1.x, V36.0.x, or V36.1.x.Affected if The installed version falls within these ranges: >= 35.1 and < 35.1.256, OR >= 36.0 and < 36.0.210, OR >= 36.1 and < 36.1.185.
-
Confirm X_T file parsing is in useDetermine whether your workflow involves opening or importing X_T files (Parasolid text format part files). Check recent file open operations, import processes, or automated scripts that handle .x_t files.Affected if X_T files are parsed or processed by the Parasolid installation.
-
Check for recent X_T file activityReview recent documents, import logs, or file history to identify if X_T files from external or untrusted sources have been opened recently.Affected if Untrusted X_T files have been opened on the affected version of Parasolid.
You are affected if the installed Parasolid version is one of the vulnerable releases (V35.1.0 through V35.1.255, V36.0.0 through V36.0.209, or V36.1.0 through V36.1.184) and X_T files are processed in your environment.
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 · scoped35.1.25636.0.21036.1.185
Update Parasolid to the patched versions (V35.1.256, V36.0.210, V36.1.185 or later) and avoid opening untrusted X_T files from unknown sources.
Parasolid V35.1.256+, V36.0.210+, or V36.1.185+ depending on your current version branch
- 1. Identify the current Parasolid version by checking the application or library version information
- 2. Determine which version line you are currently using: V35.1.x, V36.0.x, or V36.1.x
- 3. For V35.1.x users: Upgrade to V35.1.256 or later
- 4. For V36.0.x users: Upgrade to V36.0.210 or later
- 5. For V36.1.x users: Upgrade to V36.1.185 or later
- 6. After upgrading, re-test any functionality that parses X_T part files to ensure normal operation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31980 — 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-2024-31980 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