dbcve.org
Jt2goApplication · Siemens

CVE-2023-38070

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 is vulnerable to stack-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-20818)

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

Stack-based buffer overflow vulnerability in JT2Go, Teamcenter Visualization, and Tecnomatix Plant Simulation when parsing specially crafted WRL (VRML) files. Successful exploitation allows arbitrary code execution in the context of the current user process.

MitigationUpdate affected products to vendor-specified patched 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 Plant Simulation V2201.0010+/V2302.0004+. Until patched, avoid opening untrusted WRL files with vulnerable software.

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 product
    Check for presence of JT2Go, Teamcenter Visualization, or Tecnomatix Plant Simulation in the system (typically found in Program Files/Siemens). Look for the application executable or check Windows Programs and Features.
    Affected if Any of these three products is installed
  2. Determine JT2Go version
    Right-click the JT2Go application shortcut or executable, select Properties, and check the Details tab for the File Version. Alternatively, open JT2Go and go to Help > About.
    Affected if Version is present and less than 14.3.0.1
  3. Determine Teamcenter Visualization version
    Right-click the Teamcenter Visualization executable, select Properties, and check the Details tab for the File Version. Check the Siemens documentation for the specific component name if using a modular installation.
    Affected if Version falls in 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
  4. Determine Tecnomatix Plant Simulation version
    Open Tecnomatix Plant Simulation, go to Help > About, or right-click the executable and check Properties > Details for the File Version.
    Affected if Version is >= 2201.0 and < 2201.0010, OR >= 2302.0 and <= 2302.0004

A user is affected if any of these three Siemens products is installed AND the installed version falls within the affected ranges listed above.

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 vendor-specified patched 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 Plant Simulation V2201.0010+/V2302.0004+. Until patched, avoid opening untrusted WRL files with vulnerable software.

Recommended fix High confidence

JT2Go: V14.3.0.1 | Teamcenter Visualization V13.3: V13.3.0.12 | Teamcenter Visualization V14.1: V14.1.0.11 | Teamcenter Visualization V14.2: V14.2.0.6 | Teamcenter Visualization V14.3: V14.3.0.1 | Tecnomatix Plant Simulation V2201: V2201.0010 | Tecnomatix Plant Simulation V2302: V2302.0004

  1. Identify the exact product and version currently installed (JT2Go, Teamcenter Visualization, or Tecnomatix Plant Simulation)
  2. Determine which version branch the current installation belongs to (e.g., V13.3, V14.0, V14.1, V14.2, V14.3, V2201, or V2302)
  3. Obtain the appropriate fixed version from Siemens support or official channels: For JT2Go upgrade to V14.3.0.1 or later; For Teamcenter Visualization V13.3.x upgrade to V13.3.0.12; For Teamcenter Visualization V14.1.x upgrade to V14.1.0.11; For Teamcenter Visualization V14.2.x upgrade to V14.2.0.6; For Teamcenter Visualization V14.3.x upgrade to V14.3.0.1; For Tecnomatix Plant Simulation V2201.x u
  4. Download the corresponding update from Siemens PLM Downloads or through your Siemens support contract
  5. Apply the update following standard Siemens installation procedures
  6. Verify the installation was successful and the version matches the target fixed release
  7. Test that WRL file parsing functionality works correctly in the updated version
Caveat Review release notes for your specific product version to check for any feature changes or migration requirements before upgrading

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

Fix this in Jt2go Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-38070 — 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-38070 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