dbcve.org
TecnomatixApplication · Siemens

CVE-2023-37376

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 contains a type confusion vulnerability while parsing STP files. This could allow an attacker to execute code in the context of the current process. (ZDI-CAN-21051)

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 type confusion vulnerability exists in the STP file parser of Tecnomatix Plant Simulation versions prior to V2201.0008 and V2302.0002. When parsing specially crafted STP files, the application mishandles object types, potentially allowing an attacker to achieve arbitrary code execution in the context of the current process.

MitigationUpdate to version V2201.0008 or V2302.0002 and later. Avoid opening untrusted STP files from unknown or untrusted 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
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. Identify Tecnomatix Plant Simulation version
    Open the application and navigate to Help > About, or locate the executable (usually in Program Files/Siemens/Tecnomatix_PlantSimulation/bin) and check its file properties for the version number
    Affected if The version falls within < 2201.0008 or >= 2201 but < 2302.0002 (vulnerable range)
  2. Confirm STP file parsing capability is present
    Check if the application can open STP files by attempting to import an STP file or locating STP-related menu options (File > Import > STP/STEP)
    Affected if STP file import functionality exists and is accessible in the installation
  3. Verify the application executable
    Locate the main Plant Simulation executable (typically PlantSimulation.exe) and verify its digital signature and file version using Windows Explorer properties or sigcheck.exe
    Affected if The executable version matches the vulnerable version ranges listed

You are affected if Tecnomatix Plant Simulation is installed with a version prior to V2201.0008 or between V2201.x and V2302.0001, and the STP file parser feature is available in your installation.

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 version V2201.0008 or V2302.0002 and later. Avoid opening untrusted STP files from unknown or untrusted sources.

Recommended fix High confidence

Tecnomatix Plant Simulation V2201.0008 (for 2201 branch) or V2302.0002 (for 2302 branch)

  1. 1. Identify the current installed version of Tecnomatix Plant Simulation (check About or version information in the application)
  2. 2. If running V2201.x branch, download Tecnomatix Plant Simulation V2201.0008 or later from Siemens support portal
  3. 3. If running V2302.x branch, download Tecnomatix Plant Simulation V2302.0002 or later from Siemens support portal
  4. 4. Back up any existing projects and configurations before upgrading
  5. 5. Run the installer with administrative privileges
  6. 6. Follow the Siemens installation wizard to complete the upgrade
  7. 7. Verify the application launches successfully with the new version
  8. 8. Test that STP file parsing works correctly in the updated version
Caveat Standard enterprise software upgrade considerations apply - verify compatibility with dependent systems and review Siemens upgrade documentation for any specific migration requirements

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

Fix this in Tecnomatix Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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