dbcve.org
ParasolidApplication · Siemens

CVE-2024-22043

MEDIUM · 5.5 CVSS v3.1 Published 2024-02-13
Fix available
A fix is available. Upgrade to 35.0.251 / 35.1.170 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 vulnerability has been identified in Parasolid V35.0 (All versions < V35.0.251), Parasolid V35.1 (All versions < V35.1.170). The affected applications contain a null pointer dereference vulnerability while parsing specially crafted XT files. An attacker could leverage this vulnerability to crash the application causing denial of service condition.

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 confidence

A null pointer dereference vulnerability exists in Parasolid CAD software versions V35.0 (prior to V35.0.251) and V35.1 (prior to V35.1.170) when parsing specially crafted XT files. Successful exploitation causes the application to crash, resulting in a denial of service condition.

MitigationUpgrade Parasolid installation to version V35.0.251 or later for V35.0, or V35.1.170 or later for V35.1. Avoid opening untrusted XT files from unknown sources.

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
ParasolidApplication
Affected:>= 35.0, < 35.0.251>= 35.1, < 35.1.170

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 Parasolid installation
    Check for Parasolid installation by looking for the Parasolid component in your system. This may be found in CAD applications that bundle Parasolid (Siemens NX, Solid Edge, or third-party apps), or as a standalone Parasolid installation. Check program directories, or query installed software for 'Parasolid'.
    Affected if Parasolid is not installed on the system.
  2. Determine installed Parasolid version
    Locate the Parasolid version information. This is typically found in the Parasolid library file (usually named something like 'xpcd.dll' or 'Parasolid.dll') via file properties, or within the host application's about/ version information. Query the DLL version using PowerShell: Get-ItemProperty -Path 'C:\path\to\Parasolid.dll' | Select-Object VersionInfo
    Affected if Unable to determine the Parasolid version from installed files.
  3. Compare version against affected ranges
    If the Parasolid version is V35.0.x, verify it is less than V35.0.251. If the version is V35.1.x, verify it is less than V35.1.170. Any version in these ranges is vulnerable.
    Affected if Version is >=35.0.0 and <35.0.251, OR >=35.1.0 and <35.1.170.
  4. Determine XT file processing usage
    Check if the environment processes XT files, which is the Parasolid native CAD format. XT files are commonly used in CAD workflows. This is typically a core function of Parasolid-based applications.
    Affected if XT files are processed by the Parasolid installation.

The environment is affected if Parasolid is installed with version V35.0.x (<35.0.251) or V35.1.x (<35.1.170) and the software processes XT files.

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 35.0.251 / 35.1.170 or later
Fixed in 35.0.25135.1.170
Interim mitigation

Upgrade Parasolid installation to version V35.0.251 or later for V35.0, or V35.1.170 or later for V35.1. Avoid opening untrusted XT files from unknown sources.

Recommended fix High confidence

Parasolid V35.0.251 or V35.1.170 (or later)

  1. 1. Identify the current Parasolid version in use by checking the application or installation details
  2. 2. Navigate to the Siemens support portal or authorized distribution channel for Parasolid
  3. 3. Download Parasolid version 35.0.251 or version 35.1.170 (or later) based on your current version branch
  4. 4. Verify the downloaded update package integrity using checksums if provided
  5. 5. Test the update in a non-production environment to ensure compatibility with your workflows
  6. 6. Schedule a maintenance window and deploy the update to production systems
  7. 7. Validate that the application functions correctly after the update
Caveat Patch releases typically contain only bug fixes; however, validate custom configurations and workflows in non-production before upgrading

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

Fix this in Parasolid Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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