dbcve.org
ParasolidApplication · Siemens

CVE-2023-45601

HIGH · 7.8 CVSS v3.1 Published 2023-10-10
Fix available
A fix is available. Upgrade to 35.0.262 / 35.1.250 or later.
See remediation →
81/100
Remediation priority · High
No privileges Patch available

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.262), Parasolid V35.1 (All versions < V35.1.250), Parasolid V36.0 (All versions < V36.0.169), Tecnomatix Plant Simulation V2201 (All versions < V2201.0009), Tecnomatix Plant Simulation V2302 (All versions < V2302.0003). The affected applications contain a stack overflow vulnerability while parsing specially crafted IGS files. This could allow an attacker to execute code in the context of the current process. (ZDI-CAN-21290)

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
How this class of weakness works · CWE-121

Data overflows a fixed-size buffer allocated on the stack, overwriting adjacent stack memory — including saved return addresses — which is the classic route to redirecting execution into attacker-supplied code. Crafted input is all it takes. Remediation is strict length checks, safe bounded string and memory functions, and modern stack-protection mitigations.

General guidance for the stack-based buffer overflow class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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.262>= 35.1, < 35.1.250>= 36.0, < 36.0.169
TecnomatixApplication
Affected:>= 2201, < 2201.0009>= 2302, < 2302.0003

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

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.262 / 35.1.250 / 36.0.169 or later
Fixed in 35.0.26235.1.25036.0.169
Vendor patch cert-portal.siemens.com →
Recommended fix High confidence

Parasolid V35.0.262 / V35.1.250 / V36.0.169 or later; Tecnomatix Plant Simulation V2201.0009 / V2302.0003 or later

  1. 1. Identify the exact version of Parasolid or Tecnomatix Plant Simulation currently installed
  2. 2. For Parasolid: Upgrade to V35.0.262 or later if using V35.0.x branch
  3. 3. For Parasolid: Upgrade to V35.1.250 or later if using V35.1.x branch
  4. 4. For Parasolid: Upgrade to V36.0.169 or later if using V36.0.x branch
  5. 5. For Tecnomatix Plant Simulation: Upgrade to V2201.0009 or later if using V2201.x branch
  6. 6. For Tecnomatix Plant Simulation: Upgrade to V2302.0003 or later if using V2302.x branch
  7. 7. After upgrading, validate that IGS file parsing functionality works correctly
  8. 8. Apply the latest available service packs or updates for the specific version chosen
Caveat Review release notes for the target version to check for API changes or compatibility impacts with downstream systems

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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