CVE-2023-38073
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 a type confusion vulnerability while parsing WRL files. This could allow an attacker to execute code in the context of the current process. (ZDI-CAN-20826)
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 confidenceThis vulnerability is a type confusion flaw in the WRL file parser affecting multiple Siemens PLM applications (JT2Go, Teamcenter Visualization, Tecnomatix Plant Simulation). The type confusion allows an attacker to manipulate memory handling during WRL parsing, leading to arbitrary code execution in the context of the current process. The attack vector is local or via malicious WRL files.
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 applicationsCheck for JT2Go, Teamcenter Visualization, or Tecnomatix Plant Simulation in the system. On Windows, check Program Files folder or use 'Get-ItemProperty' in PowerShell for registry entries under HKLM:\SOFTWARE\Siemens or HKLM:\SOFTWARE\WOW6432Node\SiemensAffected if Any of these three applications are present on the system
-
Retrieve JT2Go versionLocate JT2Go installation directory (typically C:\Program Files\Siemens\JT2Go) and run 'JT2Go.exe /version' or right-click on JT2Go.exe, select Properties, and check the Details tab for Product VersionAffected if Version is found to be less than 14.3.0.1
-
Retrieve Teamcenter Visualization versionLocate the Teamcenter Visualization installation (common paths: C:\Program Files\Teamcenter\Visualization or C:\Siemens\Teamcenter12) and check the version via the executable's properties or run 'TcVis.exe /version' if availableAffected if Version falls within any of 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
-
Retrieve Tecnomatix Plant Simulation versionLocate Tecnomatix Plant Simulation installation (typically C:\Program Files\Siemens\Tecnomatix_Plant_Simulation) and check the version via the executable properties or look for version info in the installation directoryAffected if Version falls within these ranges: >=2201.0 and <2201.0010, OR >=2302.0 and <2302.0004
-
Confirm WRL file handling capabilityVerify the application can process WRL files by checking if the WRL file type association exists, or attempt to open a WRL file with the installed application to confirm parsing functionality is activeAffected if The application can open or parse WRL files, enabling the vulnerable code path
The environment is affected if any of the three Siemens PLM applications are installed with a version matching the affected ranges AND WRL file processing is functional.
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: Update JT2Go to V14.3.0.1, Teamcenter Visualization to the patched versions (V13.3.0.12, V14.1.0.11, V14.2.0.6, V14.3.0.1), and Tecnomatix Plant Simulation to V2201.0010 or V2302.0004. Until patched, avoid opening untrusted WRL files.
JT2Go: 14.3.0.1+ | Teamcenter Visualization: 13.3.0.12+, 14.1.0.11+, 14.2.0.6+, or 14.3.0.1+ | Tecnomatix Plant Simulation: 2201.0010+ or 2302.0004+
- 1. Identify the installed product (JT2Go, Teamcenter Visualization, or Tecnomatix Plant Simulation) and its current version
- 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.0: Upgrade to version 14.1.0.11 or later (note: V14.0 has no fix, must go to V14.1)
- 5. For Teamcenter Visualization V14.1: Upgrade to version 14.1.0.11 or later
- 6. For Teamcenter Visualization V14.2: Upgrade to version 14.2.0.6 or later
- 7. For Teamcenter Visualization V14.3: Upgrade to version 14.3.0.1 or later
- 8. For Tecnomatix Plant Simulation V2201: Upgrade to version 2201.0010 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-38073 — 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-38073 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