dbcve.org
Jt Open ToolkitApplication · Siemens

CVE-2021-44433

HIGH · 7.8 CVSS v3.1 Published 2021-12-14
Fix available
A fix is available. Upgrade to 11.1.1.0 / 13.1.1.0 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 Utilities (All versions < V13.1.1.0), JTTK (All versions < V11.1.1.0). JTTK library in affected products contains a use after free vulnerability that could be triggered while parsing specially crafted JT files. An attacker could leverage this vulnerability to execute code in the context of the current process. (ZDI-CAN-14900)

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 use-after-free vulnerability in the JTTK library (used by JT Utilities) can be triggered when parsing specially crafted JT files, allowing arbitrary code execution in the context of the current process.

MitigationUpgrade JTTK to version 11.1.1.0 or later and JT Utilities to version 13.1.1.0 or later to patch the vulnerability.

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.1.1.0
Jt UtilitiesApplication
Affected:< 13.1.1.0

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. Locate JTTK or JT Utilities installation
    Search for the Jt Open Toolkit (JTTK) or JT Utilities installation directory, typically found in Siemens software installation folders such as C:\Program Files\Siemens\ or under the application's runtime directories. Look for files named jtkit.jar, jttk.jar, or JT_Utilities executable.
    Affected if The software is found installed on the system
  2. Identify installed JTTK version
    Check the version of the JTTK library by inspecting the jar file name or manifest within the installation directory. Common locations include the lib folder within the JT installation path. Look for version information in the filename (e.g., jtkit-10.x.x.jar) or in the META-INF/MANIFEST.MF file inside the jar.
    Affected if The version is lower than 11.1.1.0
  3. Identify installed JT Utilities version
    Check the version of JT Utilities by examining the application executable, DLL files, or version information in the installation directory. Right-click on the main executable and select Properties > Details to view the File Version.
    Affected if The version is lower than 13.1.1.0
  4. Confirm vulnerability exposure
    Since the vulnerability is triggered when parsing specially crafted JT files, verify that the software has the capability to parse JT files. This is the primary function of both JTTK and JT Utilities, so any active installation capable of opening JT files is potentially vulnerable if the version check shows an affected version.
    Affected if The software can parse JT files and version is below the patched releases (JTTK < 11.1.1.0 or JT Utilities < 13.1.1.0)

A system is affected if Siemens Jt Open Toolkit version is below 11.1.1.0 or JT Utilities version is below 13.1.1.0 and the software is capable of parsing 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.1.1.0 / 13.1.1.0 or later
Fixed in 11.1.1.013.1.1.0
Interim mitigation

Upgrade JTTK to version 11.1.1.0 or later and JT Utilities to version 13.1.1.0 or later to patch the vulnerability.

Recommended fix High confidence

Jt Open Toolkit 11.1.1.0 | Jt Utilities 13.1.1.0

  1. Identify which affected product(s) are in use: Jt Open Toolkit (JTTK), JT Utilities, or both
  2. Check the currently installed version of the product(s)
  3. Navigate to the official Siemens cert-portal or Siemens support portal to obtain the fixed versions
  4. Download JTTK version 11.1.1.0 or later
  5. Download JT Utilities version 13.1.1.0 or later
  6. Backup any existing JT files or configurations as a precaution
  7. Install the upgraded version(s) following standard installation procedures
  8. Verify the installation completed successfully

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

Fix this in Jt Open Toolkit Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
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,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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