dbcve.org
Jt2goApplication · Siemens

CVE-2023-38074

HIGH · 7.8 CVSS v3.1 Published 2023-09-12
Fix available
A fix is available. Upgrade to 13.4.0.12 / 14.1.0.11 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
A 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-20840)

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 confidence

A type confusion vulnerability exists in multiple Siemens visualization products (JT2Go, Teamcenter Visualization, Tecnomatix Plant Simulation) when parsing WRL (VRML) files. The vulnerability allows an attacker to achieve code execution in the context of the current process by crafting a malicious WRL file that triggers the type confusion during parsing.

MitigationUpdate affected products to the specified minimum 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, and Tecnomatix Plant Simulation V2201 to V2201.0010, V2302 to V2302.0004. Restrict WRL file handling to trusted sources as an interim measure.

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
Jt2goApplication
Affected:< 14.3.0.1
Teamcenter VisualizationApplication
Affected:>= 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
Tecnomatix Plant SimulationApplication
Affected:>= 2201.0, < 2201.0010>= 2302.0, < 2302.0004

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Siemens visualization product
    Check the installed programs for JT2Go, Teamcenter Visualization, or Tecnomatix Plant Simulation. On Windows, use Control Panel > Programs and Features, or search for the product in the Start menu. Note the exact product name installed.
    Affected if Any of these three products are installed on the system
  2. Determine installed version of the product
    For JT2Go: Right-click the application shortcut, select Properties, and check the Details tab for the version. For Teamcenter Visualization: Open the application and navigate to Help > About, or check the installation directory for version info. For Tecnomatix Plant Simulation: Launch the application and go to Help > About, or check the installation folder for version information.
    Affected if The installed version falls within any of these ranges: JT2Go < 14.3.0.1; Teamcenter Visualization: 13.3.0 to 13.4.0.11, 14.0.0 to 14.1.0.10, 14.2.0 to 14.2.0.5, or 14.3.0; Tecnomatix Plant Simulation: 2201.0 to 2201.0009 or 2302.0 to 2302.0003
  3. Verify WRL file handling capability
    Check if the WRL file parser module is present and functional. WRL (VRML) files are a standard file format handled by these visualization products. Attempt to open a .wrl file in the installed product, or check the file association settings for .wrl files on the system.
    Affected if The product can open or parse WRL files, meaning the vulnerable parsing code is reachable
  4. Confirm active use of WRL parsing
    Search the system for .wrl files, particularly in directories accessible by the visualization product or in recent project folders. Check the product's import or file open dialogs to confirm WRL is a supported format.
    Affected if WRL files are present or the product has been used to handle WRL files, indicating the vulnerable code path could be triggered

The system is affected if any of these Siemens products (JT2Go, Teamcenter Visualization, or Tecnomatix Plant Simulation) are installed with a version matching the affected ranges and the product can process WRL files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 13.4.0.12 / 14.1.0.11 / 14.2.0.6 or later
Fixed in 13.4.0.1214.1.0.1114.2.0.6
Interim mitigation

Update affected products to the specified minimum 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, and Tecnomatix Plant Simulation V2201 to V2201.0010, V2302 to V2302.0004. Restrict WRL file handling to trusted sources as an interim measure.

Recommended fix High confidence

JT2Go: 14.3.0.1 | Teamcenter Visualization: 13.3.0.12, 14.1.0.11, 14.2.0.6, or 14.3.0.1 (depending on base version) | Tecnomatix Plant Simulation: 2201.0010 or 2302.0004

  1. 1. Identify the affected product (JT2Go, Teamcenter Visualization, or Tecnomatix Plant Simulation) and current installed version
  2. 2. For JT2Go: Upgrade to version 14.3.0.1 or later
  3. 3. For Teamcenter Visualization V13.3: Upgrade to version 13.3.0.12 or later
  4. 4. For Teamcenter Visualization V14.0: Upgrade to version 14.1.0.11 or later (V14.0 all versions affected)
  5. 5. For Teamcenter Visualization V14.1: Upgrade to version 14.1.0.11 or later
  6. 6. For Teamcenter Visualization V14.2: Upgrade to version 14.2.0.6 or later
  7. 7. For Teamcenter Visualization V14.3: Upgrade to version 14.3.0.1 or later
  8. 8. For Tecnomatix Plant Simulation V2201: Upgrade to version 2201.0010 or later
Caveat Upgrades may introduce functionality changes; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jt2go Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,780
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-38074 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-38074 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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