CVE-2022-41704 json
Apache Batik prior to 1.16 allows RCE when loading untrusted SVG input
published 4y ago modified 4mo ago also GHSA-r29w-r9ph-vm76 , EUVD-2022-7156
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.1%
- EPSS 3.1% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven org.apache.xmlgraphics:batik 1.16
- apache batik 1.16
- batik Debian 14, Debian 13, Debian 12 1.16+dfsg-1
debian advisories DEBIAN-CVE-2022-41704
- batik Ubuntu 18.04 LTS 1.10-2~18.04.1
- batik Ubuntu 20.04 LTS 1.12-1ubuntu0.1
- batik Ubuntu 22.04 LTS 1.14-1ubuntu0.2
- batik Ubuntu Pro 14.04 LTS 1.7.ubuntu-8ubuntu2.14.04.3+esm1
- batik Ubuntu Pro 16.04 LTS 1.8-3ubuntu1+esm1
ubuntu advisories UBUNTU-CVE-2022-41704
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- xmlgraphics-batik SLE Module for Development Tools 15 SP5, openSUSE Leap 15.5 1.17-150200.4.7.1
- xmlgraphics-batik SLE Software Development Kit 12 SP5 1.17-2.7.1
suse advisories SUSE-SU-2024:0808-1SUSE-SU-2024:0777-1
Is CVE-2022-41704 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-41704 updated cvss 7.5
batik: Apache XML Graphics Batik vulnerable to code execution via SVG
-
Red Hat Decision Manager 7 batikaffected: no fix planned “Out of support scope”
-
Red Hat Integration Camel K 1 batik Red Hat Integration Camel Quarkus 2 batikaffected: no fix planned “Will not fix”
-
Red Hat JBoss Data Grid 7 batik Red Hat Process Automation 7 batikaffected: no fix planned “Out of support scope”
-
Red Hat Fuse 7.12fixed: vendor fix RHSA-2023:3954
-
Red Hat RHINT Camel-Springboot 3.20.1fixed: vendor fix RHSA-2023:2100
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 8mo ago
Exploit prediction
3.10% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.xmlgraphics:batik | <1.16 |
1.16 |
Affected products
- Apache Software Foundation Apache XML Graphics
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
github.com
/apache/xmlgraphics-batik/commit/905f368b50c2567cf2c4869a0ab596a7b1b5125c
web
-
debian.org
/security/2022/dsa-5264
vendor-advisory, web, third-party-advisory
-
security.gentoo.org
/glsa/202401-11
vendor-advisory, web
-
lists.apache.org
/thread/hplhx0o74jb7blj39fm4kw3otcnjd6xf
web, vendor-advisory
-
openwall.com
/lists/oss-security/2022/10/25/2
mailing-list, web, third-party-advisory
-
lists.debian.org
/debian-lts-announce/2022/10/msg00038.html
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-41704
advisory
-
issues.apache.org
/jira/browse/BATIK-1338
web
-
xmlgraphics.apache.org
/security.html
web
-
svn.apache.org
/repos/asf/xmlgraphics/batik/trunk
web
Sources
- CVE List CVE-2022-41704
- GitHub Advisory GHSA-r29w-r9ph-vm76
- NVD CVE-2022-41704
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.