Tecnomatix Plant SimulationApplication · Siemens

CVE-2024-52573

HIGH · 7.8 CVSS v3.1 Published 2024-11-18

Fix available

A fix is available. Upgrade to 2302.0018 / 2404.0007 or later.

See remediation →

81/100

Remediation priority · High

No privileges

Official description

NVD · unedited

A vulnerability has been identified in Teamcenter Visualization V14.2 (All versions < V14.2.0.14), Teamcenter Visualization V14.3 (All versions < V14.3.0.12), Teamcenter Visualization V2312 (All versions < V2312.0008), Teamcenter Visualization V2406 (All versions < V2406.0005), Tecnomatix Plant Simulation V2302 (All versions < V2302.0018), Tecnomatix Plant Simulation V2404 (All versions < V2404.0007). The affected applications contain an out of bounds write vulnerability when parsing a specially crafted WRL file. This could allow an attacker to execute code in the context of the current process. (ZDI-CAN-24521)

Technical summary

dbcve analysis · high confidence

The vulnerability is an out-of-bounds write flaw in Teamcenter Visualization and Tecnomatix Plant Simulation when parsing WRL (VRML) files. A specially crafted WRL file with malformed data causes the parser to write beyond allocated buffer boundaries, enabling an attacker to achieve arbitrary code execution in the context of the running process. This is a classic memory corruption vulnerability in file parsing code.

MitigationApply the vendor-supplied patches by updating to Teamcenter Visualization V14.2.0.14+, V14.3.0.12+, V2312.0008+, V2406.0005+ or Tecnomatix Plant Simulation V2302.0018+, V2404.0007+ as appropriate for the deployed version.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Tecnomatix Plant SimulationApplication

Affected:< 2302.0018>= 2404.0, < 2404.0007

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Confirm Tecnomatix Plant Simulation is installed

Check for the presence of Tecnomatix Plant Simulation installation directory (typically under C:\Program Files\Siemens\Tecnomatix_Plant_Simulation or /usr/local/Siemens/Tecnomatix_Plant_Simulation) and locate the executable (PlantSimulation.exe or plant simulation executable)

Affected if Tecnomatix Plant Simulation is installed with a version less than 2302.0018, or version 2404.0 through 2404.0006
Confirm Teamcenter Visualization is installed

Check for Teamcenter Visualization installation directory (typically under C:\Program Files\Siemens\Teamcenter_Visualization or similar) and locate visualization executables

Affected if Teamcenter Visualization is installed with a version earlier than the patched releases (V14.2.0.14, V14.3.0.12, V2312.0008, or V2406.0005)
Determine installed version of Tecnomatix Plant Simulation

Open Tecnomatix Plant Simulation, go to Help > About, or check the version in the installation directory's version info file or executable properties

Affected if Version number falls below 2302.0018, or is 2404.0 through 2404.0006
Determine installed version of Teamcenter Visualization

Check the executable version properties (right-click on visualization executable > Properties > Details) or use the application's About dialog

Affected if Version is earlier than V14.2.0.14, V14.3.0.12, V2312.0008, or V2406.0005
Verify if WRL/VRML file parsing capability exists

Check if the application has functionality to import or open WRL files - look for WRL/VRML in file open dialogs, import options, or check associated file handlers for .wrl extension in the installation

Affected if The software can process WRL files and the version is within the affected ranges

You are affected if you have Tecnomatix Plant Simulation versions less than 2302.0018 or between 2404.0 and 2404.0006, or Teamcenter Visualization versions earlier than the patched releases, AND the software is capable of parsing WRL files.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 2302.0018 / 2404.0007 or later

Fixed in 2302.00182404.0007

Interim mitigation

Apply the vendor-supplied patches by updating to Teamcenter Visualization V14.2.0.14+, V14.3.0.12+, V2312.0008+, V2406.0005+ or Tecnomatix Plant Simulation V2302.0018+, V2404.0007+ as appropriate for the deployed version.

Recommended fix High confidence

Tecnomatix Plant Simulation V2302.0018 or later, or V2404.0007 or later (depending on your current version branch)

1. Identify the current installed version of Tecnomatix Plant Simulation (check About or version information in the application)
2. If running V2302.x, upgrade to V2302.0018 or later
3. If running V2404.x, upgrade to V2404.0007 or later
4. Obtain the updated installation package from Siemens support portal (cert-portal.siemens.com or official Siemens download channels)
5. Back up existing plant simulation projects and data before applying the update
6. Install the updated version following standard Siemens installation procedures
7. Verify the installation was successful and test that WRL file parsing works correctly

Caveat Ensure compatibility with existing plant simulation models and any custom integrations after upgrading

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
Implementation4.0 h
Testing4.0 h
Review / QA2.0 h

12.0 hours of engineering $2,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 $3,328.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-52573 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2024-52573?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to 2302.0018 / 2404.0007 or later

Severity 7.8 High

Exploit likelihood EPSS, next 30 days 0.3%

Affects: Tecnomatix Plant Simulation

Remediation

A high-priority fix

Fix this in Tecnomatix Plant Simulation 12 hrs · Moderate

Typical engagement from $2,080

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2024-52573 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References