CVE-2021-44445 json
A vulnerability has been identified in JT Utilities (All versions < V13.1.1.0), JTTK (All versions < V11.1.1.0).
published 2021-12-14 4 y ago modified 2026-06-17 4 mo ago also EUVD-2021-31285
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 58%
- public exploits
- 0
- none known
Summary
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 an out of bounds write past the fixed-length heap-based buffer while parsing specially crafted JT files. This could allow an attacker to execute code in the context of the current process. (ZDI-CAN-15054)
Patch / fix
- siemens jt_open_toolkit 11.1.1.0
- siemens jt_utilities 13.1.1.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-21-350-17 updated cvss 7.8
Siemens JT Utilities and JT Open Toolkit
-
Siemens JT Utilities <V13.1.1.0affected: fixed in V13.1.1.0, mitigation support.sw.siemens.com
-
Siemens JTTK <V11.1.1.0affected: fixed in V11.1.1.0, mitigation support.sw.siemens.com
Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf
Exploit prediction
0.84% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected products
- Siemens JT Utilities
- Siemens JTTK
Classification
References
-
cert-portal.siemens.com
/productcert/pdf/ssa-802578.pdf
vendor-advisory
Sources
- CVE List CVE-2021-44445
- NVD CVE-2021-44445
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.