Denial of Service Vulnerability in Apache Xerces2 Java Parser

libxerces2-java Updated 02 Oct 2025

Summary

30/10/2017
N/A
No i
High
7.5

CVE-2012-0881: Apache Xerces2 Java Parser before 2.12.0 allows remote attackers to cause a denial of service (CPU consumption) via a crafted message to an XML service, which triggers hash table collisions. Affects libxerces2-java versions 2.12.1-1 – 2.12.2-1. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Apache Xerces2 Java Parser is a library used for parsing, validating, and manipulating XML documents. It is widely used in Java applications for handling XML data. The vulnerability identified as CVE-2012-0881 allows remote attackers to cause a denial of service (CPU consumption) by sending a crafted message to an XML service, triggering hash table collisions.

Vulnerability Detail

The vulnerability in Apache Xerces2 Java Parser arises from the way it handles hash table collisions. By sending a specially crafted message to an XML service, an attacker can cause excessive CPU consumption, leading to a denial of service. This vulnerability can be exploited remotely, without requiring any authentication or user interaction. The impact of this vulnerability is limited to resource exhaustion and disruption of service availability.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no known workaround for this vulnerability. It is necessary to apply the official patch or upgrade to a fixed version of the Apache Xerces2 Java Parser library.

Conclusion

The vulnerability in Apache Xerces2 Java Parser allows remote attackers to cause a denial of service by triggering hash table collisions. To mitigate this vulnerability, it is crucial to upgrade to Apache Xerces2 Java Parser version 2.12.0 or later. Vulert's playground can be used to check if your application is affected by this vulnerability. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for libxerces2-java →

Share this vulnerability

FAQ

The vulnerability allows remote attackers to cause a denial of service by consuming excessive CPU resources, leading to service disruption.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities without requiring access to the code or installation.

No, authentication is not required. The vulnerability can be exploited remotely without any authentication or user interaction.

No, there are no known workarounds for this vulnerability. It is necessary to apply the official patch or upgrade to a fixed version of the Apache Xerces2 Java Parser library.

The CVSS score of this vulnerability is 7.5, indicating a high severity level.

Related vulnerabilities

Recent vulnerabilities recorded for libxerces2-java.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback