Xml Graphics BatikApplication · Apache
CVE-2022-44729
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedServer-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceApache XML Graphics Batik versions 1.16 and earlier contain a Server-Side Request Forgery (SSRF) vulnerability in SVG parsing. When processing malicious SVG files, the library automatically loads external resources referenced in the SVG (such as images, fonts, or scripts) without proper validation. This can lead to resource exhaustion through excessive network requests or information disclosure by forcing the server to fetch sensitive internal resources.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Xml Graphics BatikApplication
>= 1.0, <= 1.16
Debian LinuxOperating system
= 10.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Apache Batik versionLocate the batik JAR file or dependency in your project (typically batik-all-*.jar or batik-*.jar). Check the MANIFEST.MF file inside the JAR, or review your dependency management file (pom.xml, build.gradle, requirements.txt) for the batik version. Compare against the affected range 1.0 to 1.16.Affected if The installed version is 1.16 or earlier (1.0 through 1.16 inclusive).
-
Find SVG processing codeSearch your codebase for imports of org.apache.batik and classes that handle SVG documents, such as Batik's SVGParser, SVGCanvas, or TranscodingSupport. Look for code that parses or renders SVG files using Batik libraries.Affected if Your application uses Batik to parse, render, or process SVG files.
-
Determine SVG input sourceReview how SVG files reach the Batik library. Check if SVG files are uploaded by users, fetched from URLs, or loaded from untrusted sources. Look for endpoints, APIs, or file processing routines that accept SVG input.Affected if Your application processes SVG files from untrusted or external sources without prior sanitization.
-
Check network access from BatikReview network logs or proxy configurations while your application processes an SVG file containing external references (such as <image href="http://example.com/test.png"/>). Determine if Batik automatically attempts to resolve and load these external resources.Affected if Batik automatically makes outbound network requests to fetch resources referenced in SVG files.
You are affected if you are using Apache XML Graphics Batik versions 1.0 through 1.16 and your application processes untrusted SVG files that could contain external resource references.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Apache XML Graphics Batik to version 1.17 or later, which includes proper safeguards against automatic external resource loading. Alternatively, sanitize or validate all SVG input before processing.
Apache XML Graphics Batik 1.17 or later
- Identify the current Apache XML Graphics Batik library version in use by checking project dependencies (e.g., pom.xml, build.gradle, or JAR manifest)
- Upgrade Apache XML Graphics Batik to version 1.17 or later in your dependency management file
- If using Maven, update the dependency in pom.xml: change version to 1.17 or the latest available (e.g., <version>1.17</version>)
- If using Gradle, update the dependency: implementation 'org.apache.xmlgraphics:batik-all:1.17' or later
- Rebuild the application with the updated dependency
- Redeploy and test that SVG rendering and processing functionality works correctly with the new Batik version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Xml Graphics Batik
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-44729 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-44729 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data