dbcve.org
BatikApplication · Apache

CVE-2022-41704

HIGH · 7.5 CVSS v3.1 Published 2022-10-25
Fix available
A fix is available. Upgrade to 1.16 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability in Batik of Apache XML Graphics allows an attacker to run untrusted Java code from an SVG. This issue affects Apache XML Graphics prior to 1.16. It is recommended to update to version 1.16.

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 confidence

Apache XML Graphics Batik SVG library prior to version 1.16 contains a vulnerability allowing attackers to execute arbitrary Java code through maliciously crafted SVG files. The library processes embedded scripts without adequate sandboxing, enabling remote code execution when parsing untrusted SVG content.

MitigationUpgrade Apache XML Graphics to version 1.16 or later. Additionally, implement input validation to reject SVG files from untrusted sources or disable SVG script processing in Batik configuration.

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
BatikApplication
Affected:>= 1.0, < 1.16
Debian LinuxOperating system
Affected:= 10.0= 11.0

CVSS 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Batik library version
    Locate batik-*.jar files in your application classpath, lib directory, or dependencies file (pom.xml, build.gradle, requirements.txt). Check the filename for the version number or inspect the JAR manifest. Also check Debian packages with: dpkg -l | grep batik
    Affected if The installed Batik version is 1.0 or higher but lower than 1.16, or on Debian 10.0/11.0 the batik package version is below 1.16
  2. Verify SVG script processing is enabled
    Check Batik configuration files (batik.properties, batik-svg.properties) for the property 'batik.enableScripting' or similar scripting-related settings. Also inspect your application code for calls to SVGGraphics2D.getGeneratorContext() or script-enabled parser configurations.
    Affected if Script processing is explicitly enabled (set to true) or default configuration is in use with no script disabling applied
  3. Determine if application parses untrusted SVG input
    Review your application code to identify SVG parsing paths. Check if user-uploaded or externally sourced SVG files are processed without prior validation. Look for ParserConstructor, DocumentBuilder, or Batik's SVGParser to trace data flow.
    Affected if Your application accepts SVG files from untrusted sources (user uploads, external URLs, network endpoints) and passes them to Batik for rendering without sanitization

You are affected if your environment uses Apache Batik version 1.0 through 1.15 and processes SVG files from untrusted sources with script processing enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.16 or later
Fixed in 1.16
Interim mitigation

Upgrade Apache XML Graphics to version 1.16 or later. Additionally, implement input validation to reject SVG files from untrusted sources or disable SVG script processing in Batik configuration.

Recommended fix High confidence

Apache XML Graphics Batik 1.16

  1. Identify the current version of Batik (Apache XML Graphics) being used in your project or system
  2. Upgrade Batik to version 1.16 or later
  3. Verify the upgrade by checking the version of the updated library
  4. If using Debian Linux, apply the security updates for Debian 10 and 11 via apt-get update && apt-get upgrade (or apt-get install <package> to update specific packages)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Batik Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
19.0 hours of engineering $3,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,184.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41704 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-41704 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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