CVE-2021-44446
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 JT Utilities (All versions < V13.0.3.0), JTTK (All versions < V11.0.3.0). JTTK library in affected products contains an out of bounds write past the end of an allocated structure while parsing specially crafted JT files. This could allow an attacker to execute code in the context of the current process. (ZDI-CAN-14828, ZDI-CAN-14898)
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 confidenceMemory corruption vulnerability in JTTK library where an out-of-bounds write occurs when parsing specially crafted JT files, potentially allowing arbitrary code execution in the context of the current process.
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< 11.0.3.0< 13.0.3.0CVSS 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 if Jt Open Toolkit (JTTK) is installedSearch for JTTK JAR files (jtkit*.jar, jtopen*.jar) in common installation directories such as Program Files, application lib folders, or the local Maven/.m2 repository. Check the JAR manifest file (META-INF/MANIFEST.MF) for the Implementation-Version attribute.Affected if JTTK is present with version below 11.0.3.0
-
Identify if Siemens JT Utilities is installedLocate JT Utilities installation by searching for common executables (jtutils.exe, jt2gltf.exe, or similar JT conversion tools) in Program Files, Siemens installation directories, or application bin folders. Run 'jtutils.exe -version' or check the application's About dialog if available.Affected if JT Utilities is present with version below 13.0.3.0
-
Check for applications that bundle JTTKReview third-party CAD or PLM applications that may bundle the JTTK library. Inspect the application's lib directory for jtkit*.jar files and examine the JAR manifest for version information.Affected if A bundled JTTK library version below 11.0.3.0 is found
-
Determine if JT file parsing is in useReview application logs, file processing pipelines, or automated workflows that handle JT files. Identify any processes that invoke JTTK or JT Utilities for reading, converting, or exporting JT files.Affected if JT file parsing functionality is active using a vulnerable library version
The environment is affected if Siemens Jt Open Toolkit version is below 11.0.3.0 or Siemens JT Utilities version is below 13.0.3.0, and the system processes JT files from untrusted sources.
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 · scoped11.0.3.013.0.3.0
Update JT Utilities to version V13.0.3.0 or later and JTTK to version V11.0.3.0 or later. Avoid opening untrusted JT files from unknown or untrusted sources until patches are applied.
Jt Open Toolkit: >= 11.0.3.0 | Jt Utilities: >= 13.0.3.0
- Upgrade Jt Open Toolkit (JTTK) to version 11.0.3.0 or later
- Upgrade Jt Utilities to version 13.0.3.0 or later
- Obtain the updated versions from the official Siemens cert-portal or Siemens support channels
- Verify the installed version matches or exceeds the minimum fixed version after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-44446 — 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-2021-44446 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