Denial of service in Apache Xerces2GHSA-334p-wv2m-w3vp
Fix: apache/xerces2-j@0bdf77aGHSA-334p-wv2m-w3vp is a security vulnerability in xerces:xercesImpl. EPSS puts its 30-day exploitation probability at 30.4% (98th percentile). A fix is available for xerces:xercesImpl — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
xerces:xercesImplReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
XMLScanner.java in Apache Xerces2 Java, as used in Sun Java Runtime Environment (JRE) in JDK and JRE 6 before Update 15 and JDK and JRE 5.0 before Update 20, and in other products, allows remote attackers to cause a denial of service (infinite loop and application hang) via malformed XML input, as demonstrated by the Codenomicon XML fuzzing framework.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | xerces:xercesImpl | all versions | 2.10.0xerces:xercesImpl:2.10.0 |
Affected Products
xerces2 javaapacheubuntu linuxcanonicaldebian linuxdebianfedorafedoraprojectopensuseopensusejdkoracleDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for xerces:xercesImpl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update xerces:xercesImpl to 2.10.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-334p-wv2m-w3vp is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Extras for RHEL 3 | java-1.4.2-ibm-0:1.4.2.13.1-1jpp.1.el3 | RHSA-2009:1505 |
| Extras for RHEL 4 | java-1.5.0-sun-0:1.5.0.20-1jpp.1.el4 | RHSA-2009:1199 |
| Extras for RHEL 4 | java-1.6.0-sun-1:1.6.0.15-1jpp.1.el4 | RHSA-2009:1200 |
| Extras for RHEL 4 | java-1.5.0-ibm-1:1.5.0.10-1jpp.4.el4 | RHSA-2009:1236 |
| Extras for RHEL 4 | java-1.6.0-ibm-1:1.6.0.6-1jpp.3.el4 | RHSA-2009:1582 |
| JBEAP 4.2.0 for RHEL 4 | glassfish-javamail-0:1.4.2-0jpp.ep1.5.el4 | RHSA-2009:1637 |
| JBEAP 4.2.0 for RHEL 5 | glassfish-jsf-0:1.2_13-2.1.ep1.el5 | RHSA-2009:1650 |
| Red Hat Enterprise Linux 5 | java-1.6.0-openjdk-1:1.6.0.0-1.2.b09.el5 | RHSA-2009:1201 |
Frequently Asked Questions
Is GHSA-334p-wv2m-w3vp in your dependencies?
Find it across Maven, including transitive dependencies.