# CVE-2024-26275: Memory corruption in JT2Go

> An out-of-bounds read in Siemens CAD tools allows attackers to execute arbitrary code via crafted X_T files.

- **Severity:** High 7.3 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 9 Apr 2024
- **Updated:** 13 Aug 2024
- **Also known as:** GHSA-c732-w2pw-3g36

## What is CVE-2024-26275?

CVE-2024-26275 is a high-severity memory corruption vulnerability in Siemens Jt2go, published on 9 Apr 2024. 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 < V2312.0004), Parasolid V35.1 (All versions < V35.1.254), Parasolid V36.0 (All versions < V36.0.207), Parasolid V36.1 (All versions < V36.1.147), Teamcenter Visualization V14.2 (All versions < V14.2.0.12), Teamcenter Visualization V14.3 (All versions < V14.3.0.9), Teamcenter Visualization V2312 (All versions < V2312.0004). The affected applications contain an out of bounds read past the end of an allocated structure while parsing specially crafted X_T files. This could allow an attacker to execute code in the context of the current process.

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

## Which versions are affected by CVE-2024-26275?

It affects 3 products.


Products: Siemens Jt2go, Siemens Parasolid, Siemens Teamcenter Visualization.

## How do I fix CVE-2024-26275?

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

## Is CVE-2024-26275 being exploited?

There is no known exploitation of CVE-2024-26275 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-2024-26275 and fix it if it is affected.

What it is: CVE-2024-26275 is a high-severity memory corruption vulnerability in Siemens Jt2go, published on 9 Apr 2024. 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-2024-26275 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-2024-26275/ (Markdown: https://insights.sbomify.com/CVE-2024-26275/index.md)
```

## Sources

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

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