CVE-2023-38072
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 · uneditedA vulnerability has been identified in JT2Go (All versions < V14.3.0.1), Teamcenter Visualization V13.3 (All versions < V13.3.0.12), Teamcenter Visualization V14.0 (All versions), Teamcenter Visualization V14.1 (All versions < V14.1.0.11), Teamcenter Visualization V14.2 (All versions < V14.2.0.6), Teamcenter Visualization V14.3 (All versions < V14.3.0.1), Tecnomatix Plant Simulation V2201 (All versions < V2201.0010), Tecnomatix Plant Simulation V2302 (All versions < V2302.0004). The affected application contains an out of bounds write 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. (ZDI-CAN-20825)
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 confidenceThe vulnerability is an out-of-bounds write past the end of an allocated structure when parsing specially crafted WRL (VRML) files in JT2Go, Teamcenter Visualization, and Tecnomatix Plant Simulation. This memory corruption allows an attacker to achieve code execution in the context of the current process.
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< 14.3.0.1>= 13.3.0, < 13.4.0.12>= 14.0, < 14.1.0.11>= 14.2, < 14.2.0.6>= 14.3, < 14.3.0.1>= 2201.0, < 2201.0010>= 2302.0, < 2302.0004CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify which Siemens application is installedCheck for JT2Go, Teamcenter Visualization, or Tecnomatix Plant Simulation in the system program files or application directory. Look for executable files such as JT2Go.exe, TeamcenterVisualization.exe, or PlantSimulation.exe.Affected if Any of these three applications are present on the system
-
Determine JT2Go versionRight-click on JT2Go.exe, select Properties, and check the File Version in the Details tab. Alternatively, run JT2Go and check Help > About.Affected if The installed version is lower than 14.3.0.1
-
Determine Teamcenter Visualization versionCheck the executable properties for Teamcenter Visualization component, typically found in the Siemens directory. Look for file version information in the Details tab.Affected if The installed version falls within these ranges: >= 13.3.0 and < 13.4.0.12, OR >= 14.0 and < 14.1.0.11, OR >= 14.2 and < 14.2.0.6, OR >= 14.3 and < 14.3.0.1
-
Determine Tecnomatix Plant Simulation versionOpen Tecnomatix Plant Simulation, navigate to Help > About, or check the executable properties for the file version.Affected if The installed version is >= 2201.0 and < 2201.0010, OR >= 2302.0 and < 2302.0004
The environment is affected if any of these three Siemens applications is installed and its version falls within the vulnerable ranges listed above.
Generated from the published advisory. Verify against your own configuration.
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 · scoped13.4.0.1214.1.0.1114.2.0.6
Apply vendor patches: update JT2Go to V14.3.0.1, Teamcenter Visualization to V13.3.0.12/V14.1.0.11/V14.2.0.6/V14.3.0.1, and Tecnomatix Plant Simulation to V2201.0010/V2302.0004. Additionally, restrict untrusted WRL files from being processed by affected applications.
Upgrade to the minimum fixed version for your product line: Teamcenter Visualization V13.3.0.12, V14.1.0.11, V14.2.0.6, or V14.3.0.1; Jt2go V14.3.0.1; Tecnomatix Plant Simulation V2201.0010 or V2302.0004
- 1. Identify the currently installed product and version (Jt2go, Teamcenter Visualization, or Tecnomatix Plant Simulation)
- 2. Determine which product line and version branch applies to your installation
- 3. For Teamcenter Visualization V13.3: upgrade to version 13.3.0.12 or later
- 4. For Teamcenter Visualization V14.1: upgrade to version 14.1.0.11 or later
- 5. For Teamcenter Visualization V14.2: upgrade to version 14.2.0.6 or later
- 6. For Teamcenter Visualization V14.3 or Jt2go: upgrade to version 14.3.0.1 or later
- 7. For Tecnomatix Plant Simulation V2201: upgrade to version 2201.0010 or later
- 8. For Tecnomatix Plant Simulation V2302: upgrade to version 2302.0004 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-38072 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-38072 in production — separate from our analysis above.
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.
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.
- 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