# CVE-2019-17566: Server-side request forgery (SSRF) in Apache Batik

> Attackers can exploit improper input validation in Apache Batik to force the server to make arbitrary GET requests, potentially accessing internal resources.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 12 Nov 2020
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-17566, GHSA-cmx4-p4v5-hmr5, SUSE-SU-2020:1800-1, UBUNTU-CVE-2019-17566, openSUSE-SU-2020:0851-1, openSUSE-SU-2020:1043-1, openSUSE-SU-2024:11522-1

## What is CVE-2019-17566?

CVE-2019-17566 is a high-severity server-side request forgery vulnerability in Oracle Business Intelligence, published on 12 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Apache Batik is vulnerable to server-side request forgery, caused by improper input validation by the "xlink:href" attributes. By using a specially-crafted argument, an attacker could exploit this vulnerability to cause the underlying server to make arbitrary GET requests.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2019-17566?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.xmlgraphics:batik` | Maven | All versions | 1.13 |
| `org.apache.xmlgraphics:batik` | Maven | All versions | 1.13 |
| `xmlgraphics-batik` | SUSE:Linux Enterprise Software Development Kit 12 SP4 | All versions | 1.8-3.3.1 |
| `xmlgraphics-batik` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 1.8-3.3.1 |
| `xmlgraphics-batik` | SUSE:Package Hub 15 SP1 | All versions | 1.9-bp151.2.3.1 |
| `xmlgraphics-batik` | openSUSE:Leap 15.1 | All versions | 1.9-lp151.6.3.1 |
| `xmgraphics-batik` | openSUSE:Tumbleweed | All versions | 1.14-2.5 |

Products: Apache Batik, Oracle Api Gateway, Oracle Business Intelligence, Oracle Communications Application Session Controller, Oracle Communications Metasolv Solution, Oracle Communications Offline Mediation Controller, Oracle Enterprise Repository, Oracle Financial Services Analytical Applications Infrastructure, Oracle Fusion Middleware Mapviewer, Oracle Hospitality Opera 5, Oracle Hyperion Financial Reporting, Oracle Instantis Enterprisetrack, Oracle Jd Edwards Enterpriseone Tools, Oracle Retail Integration Bus, Oracle Retail Order Broker, Oracle Retail Order Management System Cloud Service, Oracle Retail Point-of-Service, Oracle Retail Returns Management.

## How do I fix CVE-2019-17566?

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

## Is CVE-2019-17566 being exploited?

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

## Other vulnerabilities in Oracle Business Intelligence

- [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-2019-17566 and fix it if it is affected.

What it is: CVE-2019-17566 is a high-severity server-side request forgery vulnerability in Oracle Business Intelligence, published on 12 Nov 2020. 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-2019-17566 in the wild and no public exploit code.

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

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

## Sources

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

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