dbcve.org
TecnomatixApplication · Siemens

CVE-2023-37375

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 stack-based buffer overflow while parsing specially crafted SPP files. This could allow an attacker to execute code in the context of the current process. (ZDI-CAN-21060)

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 stack-based buffer overflow vulnerability in Tecnomatix Plant Simulation allows code execution when parsing specially crafted SPP files. The vulnerability affects V2201 versions before 0008 and V2302 versions before 0002, with exploitation occurring in the context of the current user process.

MitigationApply vendor patches V2201.0008 or V2302.0002 and later. Avoid opening untrusted SPP 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
    Check Program Files for Siemens folder, or use Windows Registry key HKLM\SOFTWARE\Siemens\Tecnomatix_Plant_Simulation\InstallDir to find the installation path
    Affected if Installation directory exists and contains Plant Simulation executables
  2. Identify installed Plant Simulation version
    Right-click the executable (Plant_Simulation.exe or similar) in the installation folder, select Properties, and check the File Version field; alternatively, open the application and go to Help > About
    Affected if Version is 2201.xxxx where xxxx is less than 0008, or 2302.xxxx where xxxx is less than 0002
  3. Verify SPP file association exists
    Check Windows Registry under HKCR\.spp to see if SPP files are associated with Plant Simulation, or right-click any .spp file and view its 'Opens with' setting
    Affected if SPP files are associated with Tecnomatix Plant Simulation application
  4. Confirm SPP file handling is enabled
    Within Plant Simulation, go to File > Options or Settings and verify file type associations are active; also check if default settings allow automatic loading of SPP files on open
    Affected if SPP file handling is enabled in the application settings

You are affected if Plant Simulation version is 2201.x below 0008 or 2302.x below 0002 AND SPP file handling is enabled, allowing parsing of potentially untrusted SPP 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

Apply vendor patches V2201.0008 or V2302.0002 and later. Avoid opening untrusted SPP files from unknown sources until patched.

Recommended fix High confidence

Tecnomatix Plant Simulation V2201.0008 or V2302.0002

  1. Identify the current version of Tecnomatix Plant Simulation installed in your environment
  2. Back up any critical projects, simulations, or data before proceeding with the upgrade
  3. Download Tecnomatix Plant Simulation V2201.0008 or V2302.0002 from Siemens' official support portal (cert-portal.siemens.com or Siemens Support)
  4. Verify the integrity of the downloaded installer using checksums if provided
  5. Close all running instances of Tecnomatix Plant Simulation
  6. Install the fixed version following Siemens' standard installation procedures
  7. After installation, verify the version number matches the expected fixed release
  8. Test that SPP file parsing functionality works correctly with the updated version

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

Fix this in Tecnomatix 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-2023-37375 — 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-37375 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