CyberSecBulletin
CVE-2025-23397NVD status: Analyzed

Teamcenter Visualization V14.3: Improper Restriction of Operations within the Bounds of a Memory Buffer

Published Updated By the CyberSecBulletin desk

CVE-2025-23397 is a high-severity improper restriction of operations within the bounds of a memory buffer vulnerability in Teamcenter Visualization V14.3 from Siemens, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists version V14.3.0.13 as the first without the flaw, so updating Teamcenter Visualization V14.3 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.17% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Teamcenter Visualization V14.3 to V14.3.0.13 or a later version.
  2. Update Teamcenter Visualization V2312 to V2312.0009 or a later version.
  3. Update Teamcenter Visualization V2406 to V2406.0007 or a later version.
  4. Read the advisory on cert-portal.siemens.com for workarounds and exact fixed builds.
  5. Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.

Affected products and versions

VendorProductAffected versionsFixed in
SiemensTeamcenter Visualization V14.3before V14.3.0.13V14.3.0.13
SiemensTeamcenter Visualization V2312before V2312.0009V2312.0009
SiemensTeamcenter Visualization V2406before V2406.0007V2406.0007
SiemensTeamcenter Visualization V2412before V2412.0002V2412.0002
SiemensTecnomatix Plant Simulation V2302before V2302.0021V2302.0021
SiemensTecnomatix Plant Simulation V2404before V2404.0010V2404.0010
SiemensTeamcenter Visualization14.0.0 up to, but not including, 14.3.0.13; 2312.0 up to, but not including, 2312.0009; 2406.0 up to, but not including, 2406.0007; 2412.0 up to, but not including, 2412.000214.3.0.13, 2312.0009, 2406.0007, 2412.0002
SiemensTecnomatix Plant Simulation2302.0 up to, but not including, 2302.0021; 2404.0 up to, but not including, 2404.00102302.0021, 2404.0010

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
RequiredA user must take an action such as opening a file or link.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Scored by CNA (siemens.com).

Scoring systemScoreSeverityScored by
CVSS 4.07.3HighCNA (siemens.com)
CVSS 3.17.8HighCNA (siemens.com)

Official description

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 application is vulnerable to memory corruption while parsing specially crafted WRL files. This could allow an attacker to execute code in the context of the current process.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Restriction of Operations within the Bounds of a Memory Buffer

The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary.

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.

More Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerabilities (CWE-119)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Teamcenter Visualization V14.3

All Teamcenter Visualization V14.3 vulnerabilities

Recent Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerabilities

Spotted an error? Tell us.