# CVE-2017-8315: XML external entity in Eclipse

> An attacker can exploit an XML External Entity vulnerability in the Eclipse IDE parser via a malicious AndroidManifest.xml file to read sensitive data or cause denial of service.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** Yes
- **Published:** 20 Apr 2018
- **Updated:** 17 Sep 2024
- **Also known as:** DEBIAN-CVE-2017-8315, GHSA-f33m-7gg2-3cm2, UBUNTU-CVE-2017-8315

## What is CVE-2017-8315?

CVE-2017-8315 is a high-severity vulnerability in Check Point Software Technologies Ltd. Eclipse, published on 20 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Eclipse XML parser for the Eclipse IDE versions 2017.2.5 and earlier was found vulnerable to an XML External Entity attack. An attacker can exploit the vulnerability by implementing malicious code on Androidmanifest.xml.

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

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

It affects 1 product.


Products: Eclipse Ide.

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

Upgrade to a fixed version.

## Is CVE-2017-8315 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-8315 is a high-severity vulnerability in Check Point Software Technologies Ltd. Eclipse, published on 20 Apr 2018. 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-8315 in the wild and no public exploit code.

Affected product: Check Point Software Technologies Ltd. Eclipse. 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-8315/ (Markdown: https://insights.sbomify.com/CVE-2017-8315/index.md)
```

## Sources

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

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