CVE-2022-38398: Apache Batik Server-Side Request Forgery

CVE-2022-38398 · Severity: low · CVSS 3.1 · Published 2022-09-23

Apache Batik Server-Side Request Forgery

Technologies: org.apache.xmlgraphics:batik (Maven), org.apache.xmlgraphics:batik-bridge (Maven). Vendors: Maven.

Quick answers

Is CVE-2022-38398 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2022-38398 being exploited in the wild.
How severe is CVE-2022-38398?
Low severity, with a CVSS score of 3.1, published 23 September 2022.
Which products and versions are affected?
org.apache.xmlgraphics:batik (Maven) ECOSYSTEM:introduced=1.14,fixed=1.15; org.apache.xmlgraphics:batik-bridge (Maven) ECOSYSTEM:introduced=1.14,fixed=1.15.
Is there a fix for CVE-2022-38398?
Yes. org.apache.xmlgraphics:batik (Maven): upgrade to 1.15 or later; org.apache.xmlgraphics:batik-bridge (Maven): upgrade to 1.15 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-38398?
Check whether you run org.apache.xmlgraphics:batik (Maven) or org.apache.xmlgraphics:batik-bridge (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.apache.xmlgraphics:batik (Maven): upgrade to 1.15 or later
    # set org.apache.xmlgraphics:batik to 1.15 in your pom.xml or build.gradle
  • org.apache.xmlgraphics:batik-bridge (Maven): upgrade to 1.15 or later
    # set org.apache.xmlgraphics:batik-bridge to 1.15 in your pom.xml or build.gradle

Affected products

  • org.apache.xmlgraphics:batik (Maven) ECOSYSTEM:introduced=1.14,fixed=1.15
  • org.apache.xmlgraphics:batik-bridge (Maven) ECOSYSTEM:introduced=1.14,fixed=1.15

Identifiers

  • CVE-2022-38398
  • GHSA-c5xv-qc8p-mh2v

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.