Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2012-0881

xml: xerces-j2 hash table collisions CPU usage DoS (oCERT-2011-003)

Overview

Published
30 Oct 2017
Modified
20 Apr 2025
High CVE
1 Registry packages
1 OS packages
3 Linux distributions
Yes Fix available

Description

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.

Source: OX vulnerability database

Severity

7.5 · HIGH

CVSS 3.0 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Weakness: CWE-399

Affected packages · 1

Packages affected by CVE-2012-0881
EcosystemPackageVulnerableFixed in
Maven xerces:xercesimpl <2.12.0 2.12.0

Open a package to see all its vulnerabilities.

Operating systems · 10 fixes

debian 4 releases · 1 package

affected 4
libxerces2-java
debian fixes for CVE-2012-0881
ReleasePackageFixed in
11 libxerces2-java affected
12 libxerces2-java affected
13 libxerces2-java affected
14 libxerces2-java affected

echo 1 release · 1 package

affected 1
libxerces2-java
echo fixes for CVE-2012-0881
ReleasePackageFixed in
libxerces2-java affected

ubuntu 5 releases · 1 package

affected 5
libxerces2-java
ubuntu fixes for CVE-2012-0881
ReleasePackageFixed in
18.04-ESM libxerces2-java affected
20.04-ESM libxerces2-java affected
22.04 libxerces2-java affected
24.04 libxerces2-java affected
26.04 libxerces2-java affected

References

Show all 23 references

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.