CVE-2021-33717 json
A vulnerability has been identified in JT2Go (All versions < V13.2.0.1), Teamcenter Visualization (All versions < V13.2.0.1).
published 2021-08-10 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-20394
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 66%
- public exploits
- 0
- none known
Summary
A vulnerability has been identified in JT2Go (All versions < V13.2.0.1), Teamcenter Visualization (All versions < V13.2.0.1). When parsing specially crafted CGM Files, a NULL pointer deference condition could cause the application to crash. The application must be restarted to restore the service. An attacker could leverage this vulnerability to cause a Denial-of-Service condition in the application.
Patch / fix
- siemens jt2go 13.2.0.1
- siemens teamcenter_visualization 13.2.0.1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-21-222-01 updated cvss 5.5
Siemens JT2Go and Teamcenter Visualization products
-
Siemens JT2Go <V13.2.0.1affected: fixed in V13.2.0.1, mitigation plm.automation.siemens.com
-
Siemens Teamcenter Visualization <V13.2.0.1affected: fixed in V13.2.0.1, mitigation
Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf
Exploit prediction
1.11% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:N/A:P |
Affected products
- Siemens JT2Go
- Siemens Teamcenter Visualization
Classification
- Weakness
-
- CWE-476 NULL Pointer Dereference
References
-
cert-portal.siemens.com
/productcert/pdf/ssa-365397.pdf
patch, vendor-advisory
Sources
- CVE List CVE-2021-33717
- NVD CVE-2021-33717
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.