Tecnomatix Plant SimulationApplication · Siemens

CVE-2024-23804

HIGH · 7.8 CVSS v3.1 Published 2024-02-13
Fix available
A fix is available. Upgrade to 2201.0012 / 2302.0006 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.0012), Tecnomatix Plant Simulation V2302 (All versions < V2302.0006). The affected applications contain a stack overflow vulnerability while parsing specially crafted PSOBJ 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

A stack overflow vulnerability exists in Tecnomatix Plant Simulation when parsing specially crafted PSOBJ files. Successful exploitation allows an attacker to execute arbitrary code in the context of the current process.

MitigationUpdate Tecnomatix Plant Simulation to version V2201.0012 or V2302.0006 or later to remediate the vulnerability.

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
Tecnomatix Plant SimulationApplication
Affected:< 2201.0012>= 2302.0, < 2302.0006

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. Verify Tecnomatix Plant Simulation installation
    Check for the presence of the Siemens Tecnomatix Plant Simulation installation directory, typically found under C:\Program Files\Siemens\Tecnomatix_Plant_Simulation or in the Windows registry under HKLM\SOFTWARE\Siemens\Tecnomatix Plant Simulation
    Affected if The software is not installed on the system
  2. Locate installed version information
    Navigate to the installation directory and locate the version file, or check the program's properties in Add/Remove Programs. The version may also be found in the registry key HKLM\SOFTWARE\Siemens\Tecnomatix Plant Simulation\InstallDir or within the main executable file properties
    Affected if Unable to determine the installed version number
  3. Compare version against affected ranges
    Compare your installed version to the affected ranges: any version less than 2201.0012, or any version from 2302.0 up to but not including 2302.0006
    Affected if Installed version falls within < 2201.0012 or >= 2302.0 and < 2302.0006
  4. Confirm PSOBJ file handling is present
    Verify that the Plant Simulation installation includes file import capabilities for PSOBJ files, which is a native file format handled by the software
    Affected if PSOBJ file parsing functionality exists in the installation (this is standard functionality in affected versions)

User is affected if Tecnomatix Plant Simulation is installed with a version matching < 2201.0012 or >= 2302.0 to < 2302.0006 and the software can process PSOBJ 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.0012 / 2302.0006 or later
Fixed in 2201.00122302.0006
Interim mitigation

Update Tecnomatix Plant Simulation to version V2201.0012 or V2302.0006 or later to remediate the vulnerability.

Recommended fix High confidence

V2201.0012 or V2302.0006 depending on current branch

  1. 1. Identify the current installed version of Tecnomatix Plant Simulation (help > about or similar)
  2. 2. If running V2201 branch (any version < V2201.0012), upgrade to V2201.0012
  3. 3. If running V2302 branch (any version >= 2302.0 but < V2302.0006), upgrade to V2302.0006
  4. 4. Download the updated version from Siemens support portal or authorized distribution channel
  5. 5. Install the upgrade following standard Siemens installation procedures
  6. 6. Verify the installed version matches the target fixed version
  7. 7. Test that PSOBJ file parsing functionality works correctly after upgrade

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

Fix this in Tecnomatix Plant Simulation Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23804 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2024-23804 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