# CVE-2022-41662: Memory corruption in JT2Go

> An out-of-bounds read in Siemens JT2Go and Teamcenter Visualization allows attackers to execute arbitrary code via a malicious CGM file.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Nov 2022
- **Updated:** 21 Apr 2025
- **Also known as:** GHSA-2227-8m6h-q7c2

## What is CVE-2022-41662?

CVE-2022-41662 is a high-severity memory corruption vulnerability in Siemens Jt2go, published on 8 Nov 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A vulnerability has been identified in JT2Go (All versions <  V14.1.0.4), Teamcenter Visualization V13.2 (All versions < V13.2.0.12), Teamcenter Visualization V13.3 (All versions < V13.3.0.7), Teamcenter Visualization V14.0 (All versions < V14.0.0.3), Teamcenter Visualization V14.1 (All versions < V14.1.0.4). The affected products contain an out of bounds read vulnerability when parsing a CGM file. An attacker can leverage this vulnerability to execute code in the context of the current process.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2022-41662?

It affects 2 products.


Products: Siemens Jt2go, Siemens Teamcenter Visualization.

## How do I fix CVE-2022-41662?

No fix has been published for CVE-2022-41662 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-41662 being exploited?

There is no known exploitation of CVE-2022-41662 in the wild and no public exploit code.

## Other vulnerabilities in Siemens Jt2go

- [CVE-2020-26980](https://insights.sbomify.com/CVE-2020-26980/): Memory corruption in JT2Go (high 8.8)
- [CVE-2020-26982](https://insights.sbomify.com/CVE-2020-26982/): Memory corruption in JT2Go (high 8.8)
- [CVE-2020-26983](https://insights.sbomify.com/CVE-2020-26983/): Memory corruption in JT2Go (high 8.8)
- [CVE-2020-26984](https://insights.sbomify.com/CVE-2020-26984/): Memory corruption in JT2Go (high 8.8)
- [CVE-2020-26985](https://insights.sbomify.com/CVE-2020-26985/): Memory corruption in JT2Go (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41662 and fix it if it is affected.

What it is: CVE-2022-41662 is a high-severity memory corruption vulnerability in Siemens Jt2go, published on 8 Nov 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-41662 in the wild and no public exploit code.

Affected product: Siemens Jt2go. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-41662/ (Markdown: https://insights.sbomify.com/CVE-2022-41662/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-41662
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-41662
- OSV: https://osv.dev/vulnerability/CVE-2022-41662

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-41662/
Summaries are generated and may contain mistakes; the official description above is the record.