CVE-2023-38076
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-21041)
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 WRL file parsing affects multiple Siemens PLM software products (JT2Go, Teamcenter Visualization, Tecnomatix Plant Simulation). Specially crafted WRL files can trigger overflow leading to 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>= 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 installed Siemens PLM productsCheck the system for installed Siemens JT2Go, Teamcenter Visualization, or Tecnomatix Plant Simulation applications. On Windows, look in Program Files/Siemens or check Add/Remove Programs. On Linux, check common installation directories like /opt/siemens or use system package managers.Affected if Any of the three affected products are present on the system
-
Determine JT2Go versionIf JT2Go is installed, open the application and navigate to Help > About, or locate the executable (JT2Go.exe) and check its file properties for version information. The version number will be in the format like 14.x.x.x.Affected if The installed version is lower than 14.3.0.1
-
Determine Teamcenter Visualization versionIf Teamcenter Visualization is installed, locate the visualization executable (typically TcVisualization.exe or similar) and check its file properties, or access the version through the application Help > About menu. Note the full version number including all four digit groups.Affected if The installed version is 13.3.0 through 13.4.0.11, 14.0.0 through 14.1.0.10, 14.2.0 through 14.2.0.5, or 14.3.0 through 14.3.0.0
-
Determine Tecnomatix Plant Simulation versionIf Tecnomatix Plant Simulation is installed, open the application and check Help > About, or right-click the executable (PlantSimulation.exe) and select Properties to view version information. Record the full version number.Affected if The installed version is between 2201.0 and 2201.0009 inclusive, or between 2302.0 and 2302.0003 inclusive
-
Check WRL file usage capabilityVerify if the product has the ability to import or open VRML/WRL files. This is typically found in File > Open, File > Import menus, or within the application's documentation. The vulnerability triggers when parsing specially crafted WRL files.Affected if WRL file import or viewing functionality exists and is accessible in the installed product
The environment is affected if any of the three products is installed and its version falls within the specified vulnerable ranges and WRL file parsing features are accessible.
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
Update affected products to vendor-specified versions: JT2Go to V14.3.0.1, Teamcenter Visualization V13.3 to V13.3.0.12, V14.1 to V14.1.0.11, V14.2 to V14.2.0.6, V14.3 to V14.3.0.1, Tecnomatix Plant Simulation V2201 to V2201.0010, and V2302 to V2302.0004.
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, Tecnomatix Plant Simulation: 2201.0010/2302.0004)
- 1. Identify the exact product and version of the installed Siemens software (Jt2go, Teamcenter Visualization, or Tecnomatix Plant Simulation)
- 2. For Jt2go: Upgrade to version 14.3.0.1 or later
- 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: 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.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-38076 — 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-38076 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