# CVE-2017-10670: XML external entity in n/a

> An attacker can exploit an XML External Entity vulnerability in the OSCI Transport Library to read sensitive data or cause denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-g5jf-3pr8-vjwm

## What is CVE-2017-10670?

CVE-2017-10670 is a critical vulnerability in n/a, published on 30 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An XML External Entity (XXE) issue exists in OSCI-Transport 1.2 as used in OSCI Transport Library 1.6.1 (Java) and OSCI Transport Library 1.6 (.NET), exploitable by sending a crafted standard-conforming OSCI message from within the infrastructure.

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

## Which versions are affected by CVE-2017-10670?

It affects 1 product.


Products: Xoev Osci Transport Library.

## How do I fix CVE-2017-10670?

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

## Is CVE-2017-10670 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-10669](https://insights.sbomify.com/CVE-2017-10669/): Other in n/a (medium 6.5)
- [CVE-2017-10668](https://insights.sbomify.com/CVE-2017-10668/): Weak cryptography in n/a (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-10670 and fix it if it is affected.

What it is: CVE-2017-10670 is a critical vulnerability in n/a, published on 30 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-10670 in the wild and no public exploit code.

Affected product: n/a. 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-2017-10670/ (Markdown: https://insights.sbomify.com/CVE-2017-10670/index.md)
```

## Sources

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

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