Deserialization of Untrusted Data Affecting batik-javadoc package, versions *


Severity

Recommended
medium

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
18.93% (98th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL6-BATIKJAVADOC-1387872
  • published26 Jul 2021
  • disclosed23 May 2018

Introduced: 23 May 2018

CVE-2018-8013  (opens in a new tab)
CWE-502  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:6 batik-javadoc.

NVD Description

Note: Versions mentioned in the description apply only to the upstream batik-javadoc package and not the batik-javadoc package as distributed by RHEL. See How to fix? for RHEL:6 relevant fixed versions and status.

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.

References