Skip to content
Fencer Intel
critical 9.8

CVE-2018-8013 in the critical feed json

Deserialization of Untrusted Data in Apache Batik

published 2018-05-24 8 y ago modified 2026-06-17 4 mo ago also GHSA-25gw-4pcc-45cf , EUVD-2022-1909

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
18.6%
EPSS 18.6% chance of exploitation in 30 days, percentile 97%
public exploits
0
none known

Summary

In Apache Batik 1.x before 1.10, when deserializing subclass of `AbstractDocument`, the class takes a string from the inputStream as the class name which then use it to call the no-arg constructor of the class. Fix was to check the class type before calling newInstance in deserialization.

Patch / fix

  • maven org.apache.xmlgraphics:batik 1.10
  • apache batik 1.10
  • oracle communications_diameter_signaling_router 8.3
  • oracle communications_webrtc_session_controller 7.2
  • batik Debian 14, Debian 13, Debian 12 1.10-1

debian advisories DEBIAN-CVE-2018-8013

  • batik Ubuntu 14.04 LTS 1.7.ubuntu-8ubuntu2.14.04.3

ubuntu advisories UBUNTU-CVE-2018-8013

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

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-2018-8013 updated cvss 7.3

batik: information disclosure when deserializing

  • 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 switchyard switchyard Red Hat Software Collections rh-java-common-batik, rh-java-common-batik-demo, rh-java-common-batik-svgpp, rh-java-common-batik-javadoc, rh-java-common-batik-ttf2svg, rh-java-common-batik-squiggle, +2 more
    affected: no fix planned “Will not fix”
  • 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

Exploit prediction

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
maven org.apache.xmlgraphics:batik
>=1.0, <1.10
1.10

Affected products

  • Apache Software Foundation Apache Batik

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data

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.