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

> Unauthenticated attackers can exploit an XXE vulnerability to read local files and steal hashed credentials via modified SOAP requests.

- **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:** 15 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4m3j-93mg-c6g3

## What is CVE-2017-14101?

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

### Official description

A security researcher found an XML External Entity (XXE) vulnerability on the Conserus Image Repository archive solution version 2.1.1.105 by McKesson Medical Imaging Company, which is now a Change Healthcare company. An unauthenticated user supplying a modified HTTP SOAP request to the vulnerable service allows for arbitrary file read access to the local file system as well as the transmittal of the application service's account hashed credentials to a remote attacker.

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

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

It affects 1 product.


Products: Changehealthcare Conserus Image Repository.

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

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

## Is CVE-2017-14101 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-14101 is a critical vulnerability in n/a, published on 15 Dec 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-14101 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-14101/ (Markdown: https://insights.sbomify.com/CVE-2017-14101/index.md)
```

## Sources

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

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