dbcve.org
Teamcenter VisualizationApplication · Siemens

CVE-2025-23401

HIGH · 7.8 CVSS v3.1 Published 2025-03-11
Fix available
A fix is available. Upgrade to 14.3.0.13 / 2302.0021 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 Teamcenter Visualization V14.3 (All versions < V14.3.0.13), Teamcenter Visualization V2312 (All versions < V2312.0009), Teamcenter Visualization V2406 (All versions < V2406.0007), Teamcenter Visualization V2412 (All versions < V2412.0002), Tecnomatix Plant Simulation V2302 (All versions < V2302.0021), Tecnomatix Plant Simulation V2404 (All versions < V2404.0010). The affected applications contain an out of bounds read past the end of an allocated structure while parsing specially crafted WRL 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

An out-of-bounds read vulnerability exists in Teamcenter Visualization and Tecnomatix Plant Simulation applications when parsing WRL (VRML) files. The applications fail to properly validate buffer boundaries while parsing specially crafted WRL files, allowing reads past the end of allocated structures. This memory corruption can be weaponized to achieve code execution in the context of the current process.

MitigationApply vendor-supplied patches to reach the fixed versions (V14.3.0.13, V2312.0009, V2406.0007, V2412.0002, V2302.0021, V2404.0010). Restrict exposure to untrusted WRL files and consider network segmentation as compensating controls until patching is complete.

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
Teamcenter VisualizationApplication
Affected:>= 14.0.0, < 14.3.0.13>= 2312.0, < 2312.0009>= 2412.0, < 2412.0002
Tecnomatix Plant SimulationApplication
Affected:>= 2302.0, < 2302.0021>= 2404.0, < 2404.0010

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 installed Teamcenter Visualization version
    Check the application version through Windows Registry at HKLM\SOFTWARE\Siemens\Teamcenter\Visualization or by right-clicking the executable and viewing Properties > Details. Also check Add/Remove Programs for installed Siemens software.
    Affected if Version is 14.0.0 through 14.3.0.12, or 2312.0 through 2312.0008, or 2412.0 through 2412.0001
  2. Identify installed Tecnomatix Plant Simulation version
    Check the application version through Windows Registry at HKLM\SOFTWARE\Siemens\Tecnomatix\PlantSimulation or by viewing the executable properties. Also check Add/Remove Programs for installed Tecnomatix software.
    Affected if Version is 2302.0 through 2302.0020, or 2404.0 through 2404.0009
  3. Confirm WRL file parsing capability is present
    Search the installation directory for VRML or WRL-related DLLs such as vrmlparser.dll, wrlreader.dll, or similar visualization libraries. Check if the application has imported or loaded these components.
    Affected if WRL/VRML parsing libraries are present in the installation
  4. Identify WRL file processing workflows
    Search for recent .wrl files processed by the application, check application logs for WRL imports, or examine any automation scripts or integrations that handle VRML/WRL files.
    Affected if The environment processes or has recently processed WRL files from any source
  5. Check for untrusted WRL file sources
    Review network share permissions, email attachments handling, or download directories where WRL files may originate from untrusted or external sources.
    Affected if WRL files from untrusted or unknown sources can be loaded into the application

You are affected if either Teamcenter Visualization or Tecnomatix Plant Simulation is installed with a version falling within the affected ranges AND the system processes WRL/VRML 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 14.3.0.13 / 2302.0021 / 2312.0009 or later
Fixed in 14.3.0.132302.00212312.0009
Interim mitigation

Apply vendor-supplied patches to reach the fixed versions (V14.3.0.13, V2312.0009, V2406.0007, V2412.0002, V2302.0021, V2404.0010). Restrict exposure to untrusted WRL files and consider network segmentation as compensating controls until patching is complete.

Recommended fix High confidence

Teamcenter Visualization: 14.3.0.13, 2312.0009, 2412.0002 | Tecnomatix Plant Simulation: 2302.0021, 2404.0010

  1. 1. Identify the installed version of Teamcenter Visualization or Tecnomatix Plant Simulation using the application's About or version information
  2. 2. For Teamcenter Visualization: If version is >=14.0.0 and <14.3.0.13, upgrade to version 14.3.0.13 or later
  3. 3. For Teamcenter Visualization: If version is >=2312.0 and <2312.0009, upgrade to version 2312.0009 or later
  4. 4. For Teamcenter Visualization: If version is >=2412.0 and <2412.0002, upgrade to version 2412.0002 or later
  5. 5. For Tecnomatix Plant Simulation: If version is >=2302.0 and <2302.0021, upgrade to version 2302.0021 or later
  6. 6. For Tecnomatix Plant Simulation: If version is >=2404.0 and <2404.0010, upgrade to version 2404.0010 or later
  7. 7. Obtain the update from the official Siemens support portal or through your existing maintenance agreement
  8. 8. Test the upgrade in a non-production environment before deploying to production
Caveat Review Siemens release notes for compatibility requirements; ensure third-party integrations support the new version before upgrading

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

Fix this in Teamcenter Visualization Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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