# CVE-2017-5662: Improper Restriction of XML External Entity Reference in Apache Batik

> Attackers can read server files and cause denial of service via malicious SVG files in Apache Batik, potentially leading to full server compromise.

- **Severity:** High 7.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 18 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-5662, DLA-926-1, GHSA-qwgx-59jw-qfg9, UBUNTU-CVE-2017-5662, USN-3280-1

## What is CVE-2017-5662?

CVE-2017-5662 is a high-severity vulnerability in Apache Batik, published on 18 Apr 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

In Apache Batik before 1.9, files lying on the filesystem of the server which uses batik can be revealed to arbitrary users who send maliciously formed SVG files. The file types that can be shown depend on the user context in which the exploitable application is running. If the user is root a full compromise of the server - including confidential or sensitive files - would be possible. XXE can also be used to attack the availability of the server via denial of service as the references within a xml document can trivially trigger an amplification attack.

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

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

2 open source packages ship an affected version, including org.apache.xmlgraphics:batik. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.xmlgraphics:batik` | Maven | All versions | 1.9 |
| `org.apache.xmlgraphics:batik` | Maven | All versions | 1.9 |

Products: Apache Batik.

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

Upgrade org.apache.xmlgraphics:batik to 1.9 or later.

## Is CVE-2017-5662 being exploited?

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

## Other vulnerabilities in Apache Batik

- [CVE-2018-8013](https://insights.sbomify.com/CVE-2018-8013/): Deserialization of Untrusted Data in Apache Batik (critical 9.8)
- [CVE-2020-11987](https://insights.sbomify.com/CVE-2020-11987/): Server-side request forgery (SSRF) in Apache Batik (high 8.2)
- [CVE-2022-41704](https://insights.sbomify.com/CVE-2022-41704/): Apache Batik prior to 1.16 allows RCE when loading untrusted SVG input (high 7.5)
- [CVE-2022-42890](https://insights.sbomify.com/CVE-2022-42890/): Apache Batik prior to 1.16 allows RCE via scripting (high 7.5)
- [CVE-2022-40146](https://insights.sbomify.com/CVE-2022-40146/): Jar url should be blocked by DefaultScriptSecurity (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-5662 is a high-severity vulnerability in Apache Batik, published on 18 Apr 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-5662 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.xmlgraphics:batik (Maven): affected all versions; fixed in 1.9
- org.apache.xmlgraphics:batik (Maven): affected all versions; fixed in 1.9

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-5662/ (Markdown: https://insights.sbomify.com/CVE-2017-5662/index.md)
```

## Sources

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

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