dbcve.org
BatikApplication · Apache

CVE-2022-42890

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 Java code from untrusted SVG via JavaScript. This issue affects Apache XML Graphics prior to 1.16. Users are recommended to upgrade 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

A code injection vulnerability in Apache Batik's SVG processing allows attackers to execute arbitrary Java code by embedding malicious JavaScript within untrusted SVG files. The vulnerability stems from insufficient validation of scripting within SVG content.

MitigationUpgrade Apache XML Graphics to version 1.16 or later. Additionally, implement input validation to only accept SVG from trusted sources and disable JavaScript execution in SVG processing where not required.

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 version
    Locate the batik JAR file or dependency declaration (pom.xml, build.gradle) and check the version number. Common paths: WEB-INF/lib/, lib/, or Maven/Gradle dependencies.
    Affected if The installed version is lower than 1.16 (versions 1.0 through 1.15 are vulnerable)
  2. Confirm SVG processing is in use
    Search for code that uses Batik classes such as Transcoder, SVGDocument, or Graphics2D with SVG files. Look for imports like org.apache.batik.* in your codebase or application libraries.
    Affected if Your application processes SVG files using Apache Batik library classes
  3. Check if scripting is enabled in SVG processing
    Inspect your SVG transcoder configuration or SVG security settings. Look for ScriptSecurity settings, allowScripts attribute, or SecurityPolicy configurations in your Batik setup.
    Affected if JavaScript/scripting execution is permitted in your SVG processing configuration (the vulnerability requires scripting to be enabled for exploitation)
  4. Verify source trust for processed SVGs
    Review how SVG files are obtained in your application - check if they come from untrusted sources such as user uploads, external URLs, or user-generated content.
    Affected if Your application processes SVG files from untrusted or external sources without validation

You are affected if you use Apache Batik version below 1.16 to process SVG files, especially from untrusted sources, with scripting enabled in the SVG transcoder configuration.

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 only accept SVG from trusted sources and disable JavaScript execution in SVG processing where not required.

Recommended fix High confidence

Apache XML Graphics Batik version 1.16

  1. Identify the build system used for your Java project (Maven, Gradle, or direct JAR dependency)
  2. Locate the Batik dependency declaration in your project's dependency management file (pom.xml, build.gradle, etc.)
  3. Update the Batik version to 1.16
  4. For Maven: Change version from <batik-version> to 1.16, e.g., <groupId>org.apache.xmlgraphics</groupId><artifactId>batik-all</artifactId><version>1.16</version>
  5. For Gradle: Update implementation 'org.apache.xmlgraphics:batik-all:1.16'
  6. Run a clean build to download and integrate the new version
  7. Rebuild and test your application to ensure functionality remains intact
  8. If using Debian packages, run: apt update && apt upgrade (to receive security updates from Debian repositories)

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

Fix this in Batik Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-42890 — 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-42890 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