# CVE-2020-26981: XML external entity in JT2Go

> Remote attackers can disclose arbitrary files by tricking users into opening a specially crafted XML file in Siemens JT2Go or Teamcenter Visualization.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Jan 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cfxj-95gx-6rxg

## What is CVE-2020-26981?

CVE-2020-26981 is a medium-severity vulnerability in Siemens Jt2go, published on 12 Jan 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability has been identified in JT2Go (All versions < V13.1.0), Teamcenter Visualization (All versions < V13.1.0). When opening a specially crafted xml file, the application could disclose arbitrary files to remote attackers. This is because of the passing of specially crafted content to the underlying XML parser without taking proper restrictions such as prohibiting an external dtd. (ZDI-CAN-11890)

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

## Which versions are affected by CVE-2020-26981?

It affects 2 products.


Products: Siemens Jt2go, Siemens Teamcenter Visualization.

## How do I fix CVE-2020-26981?

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

## Is CVE-2020-26981 being exploited?

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

What it is: CVE-2020-26981 is a medium-severity vulnerability in Siemens Jt2go, published on 12 Jan 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-26981 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-2020-26981/ (Markdown: https://insights.sbomify.com/CVE-2020-26981/index.md)
```

## Sources

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

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