Skip to content
Fencer Intel
high 8.2

CVE-2020-11987 in the critical feed json

Server-side request forgery (SSRF) in Apache Batik

published 5y ago modified last mo. also GHSA-2h63-qp69-fwvw , EUVD-2022-0426

cvss
8.2
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
13.6%
EPSS 13.6% chance of exploitation in 30 days, percentile 96%
public exploits
0
none known

Summary

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

Patch / fix

  • maven org.apache.xmlgraphics:batik-svgbrowser 1.14
  • batik Debian 14, Debian 13, Debian 12 1.14-1

debian advisories DEBIAN-CVE-2020-11987

  • batik Ubuntu 18.04 LTS 1.10-2~18.04.1
  • batik Ubuntu 20.04 LTS 1.12-1ubuntu0.1
  • batik Ubuntu Pro 14.04 LTS 1.7.ubuntu-8ubuntu2.14.04.3+esm1
  • batik Ubuntu Pro 16.04 LTS 1.8-3ubuntu1+esm1

ubuntu advisories UBUNTU-CVE-2020-11987

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • xmlgraphics-batik SLE Software Development Kit 12 SP5 1.17-2.7.1

suse advisories SUSE-SU-2024:0777-1

  • java-batik Arch Linux 1.14-1

arch linux advisories AVG-1617

Is CVE-2020-11987 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-11987 updated cvss 8.2

batik: SSRF due to improper input validation by the NodePickerPanel

  • Red Hat Enterprise Linux 6 batik, batik-demo, batik-svgpp, batik-javadoc, batik-ttf2svg, batik-squiggle, +2 more Red Hat Enterprise Linux 7 batik, batik-demo, batik-svgpp, batik-javadoc, batik-ttf2svg, batik-squiggle, +2 more Red Hat JBoss Fuse 6 batik
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat Fuse 7.10
    fixed: vendor fix RHSA-2021:5134
  • Red Hat Enterprise Linux 8 batik-css, batik-util
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
last mo.

Exploit prediction

13.64% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
NVD 2.0 6.4 AV:N/AC:L/Au:N/C:P/I:P/A:N
GitHub 3.1 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.xmlgraphics:batik-svgbrowser
<1.14
1.14

Affected products

  • n/a Apache Batik

Classification

Weakness
  • CWE-20 Improper Input Validation
  • CWE-918 Server-Side Request Forgery

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.