dbcve.org
Jt Open ToolkitApplication · Siemens

CVE-2022-47936

HIGH · 7.8 CVSS v3.1 Published 2023-02-14
Fix available
A fix is available. Upgrade to 11.2.3.0 / 34.0.252 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 JT Open (All versions < V11.2.3.0), JT Utilities (All versions < V13.2.3.0), Parasolid V34.0 (All versions < V34.0.252), Parasolid V34.1 (All versions < V34.1.242), Parasolid V35.0 (All versions < V35.0.170), Parasolid V35.1 (All versions < V35.1.150). The affected application contains a stack overflow vulnerability while parsing specially crafted JT files. This could allow an attacker to execute code in the context of the current process.

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 stack overflow vulnerability exists in multiple versions of JT Open, JT Utilities, and Parasolid when parsing specially crafted JT files. The overflow occurs during JT file parsing and can allow an attacker to execute arbitrary code in the context of the current process.

MitigationUpdate affected software to the patched versions: JT Open to V11.2.3.0 or later, JT Utilities to V13.2.3.0 or later, and Parasolid to V34.0.252, V34.1.242, V35.0.170, or V35.1.150 respectively. Implement input validation and restrict processing of untrusted JT files until patches are applied.

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
Jt Open ToolkitApplication
Affected:< 11.2.3.0
Jt UtilitiesApplication
Affected:< 11.2.3.0
ParasolidApplication
Affected:>= 34.0, < 34.0.252>= 34.1, < 34.1.242>= 35.0, < 35.0.170>= 35.1, < 35.1.150

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 JT-related software
    Check system for installed JT Open Toolkit, JT Utilities, or Parasolid by reviewing installed programs in Control Panel or using 'wmic product get name' command
    Affected if One or more of these products are installed
  2. Determine JT Open Toolkit version
    Navigate to the JT Open Toolkit installation directory (typically C:\Program Files\Siemens\JT Open Toolkit or similar) and locate version information in the file properties or a version.txt file
    Affected if Installed version is found to be less than 11.2.3.0
  3. Determine JT Utilities version
    Navigate to the JT Utilities installation directory and locate version information in the file properties, README, or version manifest
    Affected if Installed version is found to be less than 11.2.3.0
  4. Determine Parasolid version
    Locate the Parasolid installation directory (commonly in CAD application folders under Program Files) and check version information in the component DLL or version file
    Affected if Installed version falls within any of these ranges: 34.0.x where x < 252, 34.1.x where x < 242, 35.0.x where x < 170, or 35.1.x where x < 150
  5. Confirm JT file parsing is in use
    Check if the software is configured to process JT files - look for recent JT file operations, check associated file associations, or review application logs if available
    Affected if The vulnerable product is actively processing JT files

You are affected if any of these products are installed with a version below the patched thresholds AND the software is used to parse JT 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 11.2.3.0 / 34.0.252 / 34.1.242 or later
Fixed in 11.2.3.034.0.25234.1.242
Interim mitigation

Update affected software to the patched versions: JT Open to V11.2.3.0 or later, JT Utilities to V13.2.3.0 or later, and Parasolid to V34.0.252, V34.1.242, V35.0.170, or V35.1.150 respectively. Implement input validation and restrict processing of untrusted JT files until patches are applied.

Recommended fix High confidence

Jt Open Toolkit and Utilities: V11.2.3.0+ | Parasolid: V34.0.252+, V34.1.242+, V35.0.170+, V35.1.150+

  1. Identify which affected product(s) are in use: Jt Open Toolkit, Jt Utilities, and/or Parasolid
  2. For Jt Open Toolkit: Upgrade to version 11.2.3.0 or later
  3. For Jt Utilities: Upgrade to version 11.2.3.0 or later
  4. For Parasolid V34.0 series: Upgrade to version 34.0.252 or later
  5. For Parasolid V34.1 series: Upgrade to version 34.1.242 or later
  6. For Parasolid V35.0 series: Upgrade to version 35.0.170 or later
  7. For Parasolid V35.1 series: Upgrade to version 35.1.150 or later
  8. Obtain updates from the official Siemens cert-portal or authorized distribution channels

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

Fix this in Jt Open Toolkit Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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