dbcve.org
Teamcenter VisualizationApplication · Siemens

CVE-2025-32454

HIGH · 7.8 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 14.3.0.14 / 2312.0010 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.14), Teamcenter Visualization V2312 (All versions < V2312.0010), Teamcenter Visualization V2406 (All versions < V2406.0008), Teamcenter Visualization V2412 (All versions < V2412.0004), Tecnomatix Plant Simulation V2404 (All versions < V2404.0013). 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 the WRL file parser of affected Teamcenter Visualization and Tecnomatix Plant Simulation applications. By parsing a specially crafted WRL file, an attacker can read beyond the bounds of an allocated memory structure, potentially achieving arbitrary code execution in the context of the current process.

MitigationApply vendor-supplied patches (V14.3.0.14, V2312.0010, V2406.0008, V2412.0004, V2404.0013 or later) to fix the WRL parsing vulnerability. Until patched, avoid opening untrusted WRL files from unknown 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
Teamcenter VisualizationApplication
Affected:>= 14.3, < 14.3.0.14>= 2312.0, < 2312.0010>= 2406.0, < 2406.008>= 2412.0, < 2412.0004
Tecnomatix Plant SimulationApplication
Affected:>= 2404.0, < 2404.0013

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 Teamcenter Visualization installation
    Locate Teamcenter Visualization on the system and determine its installed version using system software inventory, about dialog, or version information in the installation directory
    Affected if The installed version falls within any of these ranges: >= 14.3.0.0 and < 14.3.0.14, >= 2312.0.0 and < 2312.0010, >= 2406.0.0 and < 2406.0008, or >= 2412.0.0 and < 2412.0004
  2. Identify Tecnomatix Plant Simulation installation
    Locate Tecnomatix Plant Simulation on the system and determine its installed version using system software inventory, about dialog, or version information in the installation directory
    Affected if The installed version is >= 2404.0.0 and < 2404.0013
  3. Compare versions against affected ranges
    Take the discovered version numbers and compare them against the vulnerable version ranges provided in the CVE
    Affected if Any version matches an affected range listed in the CVE, indicating the WRL file parser component contains the vulnerability

If either Teamcenter Visualization or Tecnomatix Plant Simulation is installed and its version falls within the affected ranges, the environment is vulnerable to the WRL parsing out-of-bounds read.

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.14 / 2312.0010 / 2404.0013 or later
Fixed in 14.3.0.142312.00102404.0013
Interim mitigation

Apply vendor-supplied patches (V14.3.0.14, V2312.0010, V2406.0008, V2412.0004, V2404.0013 or later) to fix the WRL parsing vulnerability. Until patched, avoid opening untrusted WRL files from unknown sources.

Recommended fix High confidence

Teamcenter Visualization: V14.3.0.14, V2312.0010, V2406.0008, V2412.0004; Tecnomatix Plant Simulation: V2404.0013

  1. Identify the installed version of Teamcenter Visualization or Tecnomatix Plant Simulation
  2. Determine which product line and version is affected by checking the installed software
  3. Schedule an upgrade during a maintenance window
  4. Back up current installation and any custom configurations
  5. Upgrade to the minimum fixed version: Teamcenter Visualization V14.3.0.14 or higher, V2312.0010 or higher, V2406.0008 or higher, V2412.0004 or higher; Tecnomatix Plant Simulation V2404.0013 or higher
  6. Verify the upgrade completed successfully
  7. Test that WRL file parsing functionality works correctly with the updated version
Caveat Point releases typically maintain backward compatibility; test custom configurations and integrations before production deployment

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
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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