CVE-2023-38075
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 use-after-free vulnerability that could be triggered while parsing specially crafted WRL files. An attacker could leverage this vulnerability to execute code in the context of the current process. (ZDI-CAN-20842)
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 confidenceA use-after-free vulnerability exists in JT2Go, Teamcenter Visualization, and Tecnomatix Plant Simulation when parsing specially crafted WRL (VRML) files. The vulnerability allows an attacker to execute arbitrary code in the context of the current process by exploiting the freed memory access.
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 visualization productsCheck if Siemens Jt2go, Teamcenter Visualization, or Tecnomatix Plant Simulation is installed on the system. Look in standard installation directories such as C:\Program Files\Siemens or check Add/Remove Programs for these product names.Affected if Any of these three products is present on the system
-
Determine installed version of Jt2GoOpen Jt2Go and navigate to Help > About, or right-click the executable and view Properties > Details to find the version number.Affected if Version is present and less than 14.3.0.1
-
Determine installed version of Teamcenter VisualizationOpen Teamcenter Visualization and check Help > About, or locate the installation directory and find version information in the product release notes or manifest files.Affected if Version is present and falls within any of these ranges: 13.3.0 to 13.3.0.11, 14.0.0 to 14.1.0.10, 14.2.0 to 14.2.0.5, or 14.3.0 to 14.3.0.0
-
Determine installed version of Tecnomatix Plant SimulationOpen Tecnomatix Plant Simulation and check Help > About, or locate the installation directory and review version information in the software metadata or release notes.Affected if Version is present and falls within either of these ranges: 2201.0 to 2201.0009 or 2302.0 to 2302.0003
If any of the three products is installed and the version falls within the affected ranges listed above, the environment is vulnerable when parsing untrusted WRL 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
Update all affected software to the specified patched 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, V2302 to V2302.0004). Avoid opening untrusted WRL files until patching is complete.
JT2Go: V14.3.0.1 | Teamcenter Visualization: V13.3.0.12, V14.1.0.11, V14.2.0.6, or V14.3.0.1 (depending on branch) | Tecnomatix Plant Simulation: V2201.0010 or V2302.0004
- Identify the affected Siemens product (JT2Go, Teamcenter Visualization, or Tecnomatix Plant Simulation) and determine the current installed version
- For Teamcenter Visualization, determine which version branch is installed: V13.3.x, V14.0.x, V14.1.x, V14.2.x, or V14.3.x
- For Tecnomatix Plant Simulation, determine which version branch is installed: V2201.x or V2302.x
- Download the corresponding fixed version from Siemens official support portal (cert-portal.siemens.com or siemens.com/support-downloads)
- Install the appropriate fixed version: JT2Go: upgrade to V14.3.0.1 or later; Teamcenter Visualization V13.3: upgrade to V13.3.0.12 or later; Teamcenter Visualization V14.0/V14.1: upgrade to V14.1.0.11 or later; Teamcenter Visualization V14.2: upgrade to V14.2.0.6 or later; Teamcenter Visualization V14.3: upgrade to V14.3.0.1 or later; Tecnomatix Plant Simulation V2201: upgrade to V2201.0010 or lat
- Verify the installation by checking the application's version information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-38075 — 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-38075 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