dbcve.org
TecnomatixApplication · Siemens

CVE-2023-37247

HIGH · 7.8 CVSS v3.1 Published 2023-07-11
Fix available
A fix is available. Upgrade to 2201.0008 / 2302.0002 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 Tecnomatix Plant Simulation V2201 (All versions < V2201.0008), Tecnomatix Plant Simulation V2302 (All versions < V2302.0002). The affected application is vulnerable to heap-based buffer overflow while parsing specially crafted PAR files. This could allow an attacker to execute code in the context of the current process. (ZDI-CAN-21138)

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

Heap-based buffer overflow vulnerability in Tecnomatix Plant Simulation's PAR file parser allows attackers to execute arbitrary code via specially crafted PAR files containing oversized data that overflows heap allocations.

MitigationUpdate to V2201.0008 or V2302.0002 or later to patch the vulnerable PAR file parsing code; avoid opening untrusted PAR files from unknown sources 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
TecnomatixApplication
Affected:>= 2201, < 2201.0008>= 2302, < 2302.0002

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. Locate Tecnomatix Plant Simulation installation directory
    Check the default installation path (typically C:\Program Files\Siemens\Tecnomatix_Plant_Simulation\) or search for 'PlantSimulation.exe' using the Windows file explorer or Get-ChildItem cmdlet
    Affected if The software is installed in the environment
  2. Identify installed version number
    Right-click on PlantSimulation.exe, select Properties, and view the 'File version' field in the Details tab. Alternatively, run 'siemenscmd' or check Windows Registry under HKLM\SOFTWARE\Siemens\Tecnomatix\PlantSimulation for the installed version
    Affected if The version displayed is lower than the patched releases
  3. Compare version against affected ranges
    Check if the installed version falls within: 2201.0000 through 2201.0007, or 2302.0000 through 2302.0001. Versions outside these ranges (including 2201.0008+ and 2302.0002+) are not affected
    Affected if The installed version is >= 2201 and < 2201.0008, OR >= 2302 and < 2302.0002
  4. Verify PAR file handling capability
    Confirm that the installation includes the PAR file parser component by attempting to open any existing .par file or checking if the software's file open dialog shows .par as a supported format
    Affected if PAR file support is present and the version is in the affected range

User is affected if Tecnomatix Plant Simulation is installed with a version between 2201.0000-2201.0007 or 2302.0000-2302.0001 and can process PAR 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 2201.0008 / 2302.0002 or later
Fixed in 2201.00082302.0002
Interim mitigation

Update to V2201.0008 or V2302.0002 or later to patch the vulnerable PAR file parsing code; avoid opening untrusted PAR files from unknown sources until patched.

Recommended fix High confidence

V2201.0008 or V2302.0002 (depending on your version branch)

  1. 1. Identify the currently installed version of Tecnomatix Plant Simulation (check Help > About or the installation directory version info)
  2. 2. Determine which version branch you are on (V2201.x or V2302.x)
  3. 3. Download the fixed version from Siemens: upgrade to V2201.0008 (or later V2201 version) if on the V2201 branch, or V2302.0002 (or later V2302 version) if on the V2302 branch
  4. 4. Backup your current installation and any critical PAR files before upgrading
  5. 5. Install the updated version following Siemens standard installation procedures
  6. 6. Verify the version upgrade was successful after installation

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

Fix this in Tecnomatix Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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