CVE-2023-38071
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 is vulnerable to heap-based buffer overflow while parsing specially crafted WRL files. This could allow an attacker to execute code in the context of the current process. (ZDI-CAN-20824)
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 confidenceHeap-based buffer overflow vulnerability in JT2Go, Teamcenter Visualization, and Tecnomatix Plant Simulation when parsing specially crafted WRL (VRML 3D graphics) files. Successful exploitation allows arbitrary 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>= 2021.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.
-
Check JT2Go versionOpen JT2Go and navigate to Help > About JT2Go, or check the application's version property in the Windows program files directoryAffected if The installed version is lower than 14.3.0.1
-
Check Teamcenter Visualization versionOpen Teamcenter Visualization or check the program's version through the Windows installed programs list or executable propertiesAffected if The installed version is 13.3.0 through 13.4.0.11, 14.0 through 14.1.0.10, 14.2 through 14.2.0.5, or 14.3 through 14.3.0.0 (anything below 14.3.0.1 within the listed ranges)
-
Check Tecnomatix Plant Simulation versionOpen Tecnomatix Plant Simulation and check the version through Help > About, or check the installation directory for version informationAffected if The installed version is 2021.0 through 2201.0009, or 2302.0 through 2302.0003 (anything below 2201.0010 or 2302.0004 respectively)
-
Verify WRL file handling capabilityAttempt to open or import a WRL (VRML) file within the installed Siemens application, or check if the WRL file type association is enabledAffected if The application can parse WRL files and the WRL parsing module is active
You are affected if any of these products are installed at a version within the affected ranges AND the WRL file parsing feature is available and can be used to open untrusted files.
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-provided patches to update all affected products to the specified minimum versions (JT2Go V14.3.0.1, Teamcenter Visualization V13.3.0.12/V14.1.0.11/V14.2.0.6/V14.3.0.1, Tecnomatix V2201.0010/V2302.0004). Until patches are applied, restrict handling of untrusted WRL files and disable WRL preview functionality where possible.
Upgrade to the minimum fixed version for your product line (Jt2go: 14.3.0.1, Teamcenter Visualization: 13.3.0.12/14.1.0.11/14.2.0.6/14.3.0.1 depending on branch, Tecnomatix Plant Simulation: 2201.0010 or 2302.0004 depending on branch)
- Identify the exact product and version of Jt2go, Teamcenter Visualization, or Tecnomatix Plant Simulation currently installed
- Download the appropriate fixed version from Siemens cert-portal or official channels
- For Jt2go: upgrade to version 14.3.0.1 or later
- For Teamcenter Visualization V13.3: upgrade to version 13.3.0.12 or later
- For Teamcenter Visualization V14.1: upgrade to version 14.1.0.11 or later
- For Teamcenter Visualization V14.2: upgrade to version 14.2.0.6 or later
- For Teamcenter Visualization V14.3: upgrade to version 14.3.0.1 or later
- For Tecnomatix Plant Simulation V2201: upgrade to version 2201.0010 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-38071 — 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-38071 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