Skip to content

Apache XML Graphics Batik Server-Side Request Forgery vulnerability

High severity GitHub Reviewed Published Aug 22, 2023 to the GitHub Advisory Database • Updated Jan 8, 2024

Package

maven org.apache.xmlgraphics:batik-bridge (Maven)

Affected versions

>= 1.0, < 1.17

Patched versions

1.17
maven org.apache.xmlgraphics:batik-svgrasterizer (Maven)
>= 1.0, < 1.17
1.17
maven org.apache.xmlgraphics:batik-transcoder (Maven)
>= 1.0, < 1.17
1.17

Description

Server-Side Request Forgery (SSRF) vulnerability in Apache Software Foundation Apache XML Graphics Batik.This issue affects Apache XML Graphics Batik: 1.16.

On version 1.16, a malicious SVG could trigger loading external resources by default, causing resource consumption or in some cases even information disclosure. Users are recommended to upgrade to version 1.17 or later.

References

Published by the National Vulnerability Database Aug 22, 2023
Published to the GitHub Advisory Database Aug 22, 2023
Reviewed Aug 23, 2023
Last updated Jan 8, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H

EPSS score

0.138%
(50th percentile)

Weaknesses

CVE ID

CVE-2022-44729

GHSA ID

GHSA-gq5f-xv48-2365

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.