CVE-2020-11987: Server-side request forgery (SSRF) in Apache Batik

Summary

06/01/2022
Yes i
High
8.2

CVE-2020-11987: Server-side request forgery (SSRF) in Apache Batik. Affects org.apache.xmlgraphics:batik-svgbrowser versions < 1.14. Fixed in 1.14. How to fix ↓

Also tracked for

The same CVE-2020-11987 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Apache Batik is an open-source Java-based toolkit for rendering SVG images. It provides a set of APIs and utilities for manipulating and displaying SVG content. The vulnerability in Apache Batik version 1.13 is related to server-side request forgery (SSRF), which occurs due to improper input validation by the NodePickerPanel. This vulnerability allows an attacker to manipulate the server into making arbitrary GET requests.

Vulnerability Detail

The server-side request forgery (SSRF) vulnerability in Apache Batik 1.13 arises from the NodePickerPanel's lack of proper input validation. By exploiting this vulnerability, an attacker can craft a specially-crafted argument to trick the server into making arbitrary GET requests. This can lead to various security issues, such as unauthorized access to internal resources, information disclosure, and potential remote code execution.

How To Fix

Minimum fixed version

1.14

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, it is advised to implement server-side input validation and sanitization to prevent malicious input from being processed by the NodePickerPanel. Additionally, network-level protections, such as firewalls and network segmentation, can help mitigate the risk of SSRF attacks.

Conclusion

Apache Batik version 1.13 is vulnerable to server-side request forgery (SSRF), which can lead to unauthorized access, information disclosure, and potential remote code execution. It is crucial to upgrade to Apache Batik version 1.14 or later to mitigate this vulnerability. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for org.apache.xmlgraphics:batik-svgbrowser →

Share this vulnerability

FAQ

Apache Batik is a Java-based toolkit for rendering and manipulating SVG images.

Server-side request forgery (SSRF) is a vulnerability that allows an attacker to manipulate a server into making arbitrary requests on behalf of the server itself.

This vulnerability can lead to unauthorized access to internal resources, information disclosure, and potential remote code execution.

To fix this vulnerability, upgrade to Apache Batik version 1.14 or later.

Implement server-side input validation and sanitization, and consider network-level protections such as firewalls and network segmentation.

How To Fix

Minimum fixed version

1.14

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback