dbcve.org
ParasolidApplication · Siemens

CVE-2023-38529

HIGH · 7.8 CVSS v3.1 Published 2023-08-08
Fix available
A fix is available. Upgrade to 14.1.0.11 / 14.2.0.6 or later.
See remediation →
81/100
Remediation priority · High
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 V34.1 (All versions < V34.1.258), Parasolid V35.0 (All versions < V35.0.254), Parasolid V35.1 (All versions < V35.1.184), Teamcenter Visualization V14.1 (All versions), Teamcenter Visualization V14.2 (All versions < V14.2.0.12), Teamcenter Visualization V14.3 (All versions < V14.3.0.9), Teamcenter Visualization V2312 (All versions < V2312.0004). The affected applications contain an out of bounds read past the end of an allocated structure while parsing specially crafted X_T files. This could allow an attacker to execute code in the context of the current process.

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

An out-of-bounds read vulnerability exists in Parasolid and Teamcenter Visualization products when parsing specially crafted X_T files. The vulnerability occurs when the parser reads past the end of an allocated memory structure, potentially allowing an attacker to execute arbitrary code in the context of the current process.

MitigationApply the vendor patches: update Parasolid to V34.1.258/V35.0.254/V35.1.184 or later, and Teamcenter Visualization to V14.2.0.12/V14.3.0.9/V2312.0004 or later. Avoid opening untrusted X_T files until patched.

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:>= 34.1, < 34.1.258>= 35.0, < 35.0.254>= 35.1, < 35.1.184
Teamcenter VisualizationApplication
Affected:>= 14.1, < 14.1.0.11>= 14.2, < 14.2.0.6>= 14.3, < 14.3.0.3

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
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 checks

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

  1. Identify Parasolid version
    Check the Parasolid component version through the host application (e.g., NX, Solid Edge, or other Siemens products using Parasolid). Look in the application's About dialog, help menu, or system information. Alternatively, check the Parasolid library file version (typically parasolid.dll or similar) in the installation directory.
    Affected if The installed Parasolid version falls within: 34.1.x (before 34.1.258), 35.0.x (before 35.0.254), or 35.1.x (before 35.1.184).
  2. Identify Teamcenter Visualization version
    Check the Teamcenter Visualization version through the Teamcenter client or server. Access the system information or About section in the Teamcenter application, or check the installation directory for version information in the product files.
    Affected if The installed Teamcenter Visualization version falls within: 14.1.x (before 14.1.0.11), 14.2.x (before 14.2.0.6), or 14.3.x (before 14.3.0.3).
  3. Determine if X_T file parsing is in use
    Review whether the environment processes X_T (Parasolid text) files. Check if users or automated workflows import, open, or convert X_T files using the affected Parasolid or Teamcenter Visualization components.
    Affected if X_T file parsing is enabled and the software processes X_T files from any source.

You are affected if you have Parasolid versions 34.1.x before 34.1.258, 35.0.x before 35.0.254, or 35.1.x before 35.1.184; OR Teamcenter Visualization versions 14.1.x before 14.1.0.11, 14.2.x before 14.2.0.6, or 14.3.x before 14.3.0.3, and the software is configured to parse X_T 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 14.1.0.11 / 14.2.0.6 / 14.3.0.3 or later
Fixed in 14.1.0.1114.2.0.614.3.0.3
Interim mitigation

Apply the vendor patches: update Parasolid to V34.1.258/V35.0.254/V35.1.184 or later, and Teamcenter Visualization to V14.2.0.12/V14.3.0.9/V2312.0004 or later. Avoid opening untrusted X_T files until patched.

Recommended fix High confidence

Parasolid: V34.1.258, V35.0.254, or V35.1.184 (depending on release line in use); Teamcenter Visualization: V14.1.0.11, V14.2.0.12, V14.3.0.9, or V2312.0004 (depending on version line in use)

  1. 1. Identify the exact version of Parasolid and/or Teamcenter Visualization currently installed in your environment.
  2. 2. For Parasolid: Determine which V34.1, V35.0, or V35.1 release line is in use and upgrade to the latest corresponding fixed version.
  3. 3. For Teamcenter Visualization: Identify which version line (V14.1, V14.2, V14.3, or V2312) is in use and upgrade to the fixed release.
  4. 4. Obtain the upgrade packages from the official Siemens support portal or through your existing support contract.
  5. 5. Apply the upgrade following standard Siemens installation procedures, ensuring proper backup of existing configurations.
  6. 6. Verify the installation by confirming the new version numbers match the fixed releases.
Caveat Upgrades within the same major version should be low-risk; however, always test in a non-production environment first as minor version upgrades may introduce subtle behavioral changes

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

Fix this in Parasolid Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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 locally
dbcve dependency scanner

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