How severe is CVE-2012-0213?

No CVSS score has been assigned to CVE-2012-0213 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2012-0213?

CVE-2012-0213 affects the following packages: org.apache.poi:poi (Maven), org.apache.poi:poi-scratchpad (Maven). Ecosystems affected: Maven.

How do I fix CVE-2012-0213?

Update org.apache.poi:poi to 3.10-beta1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-0213 is resolved across your whole dependency graph.

How do I detect CVE-2012-0213 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.poi:poi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2012-0213 if there is no patch (or I can't update yet)?

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.

Is CVE-2012-0213 actively exploited in the wild?

No public exploit code has been indexed for CVE-2012-0213 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2012-0213?

CVE-2012-0213 has an EPSS (Exploit Prediction Scoring System) score of 7.5%, placing it in the 95th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2012-0213?

CVE-2012-0213 is classified as CWE-399 (CWE-399). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2012-0213 published, and has it been updated?

CVE-2012-0213 was published on May 4, 2022 and was last updated on December 3, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2012-0213 — poi

Fix: apache/poi@25bc679

CVE-2012-0213 is a CWE-399 vulnerability in org.apache.poi:poi. A fix is available for org.apache.poi:poi — see the affected versions and patch details below.

Denial of Service in Apache POI

Published

May 4, 2022

Updated

Dec 3, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

7.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

☕org.apache.poi:poi☕org.apache.poi:poi-scratchpad

Real-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

The UnhandledDataStructure function in hwpf/model/UnhandledDataStructure.java in Apache POI 3.8 and earlier allows remote attackers to cause a denial of service (OutOfMemoryError exception and possibly JVM destabilization) via a crafted length value in a Channel Definition Format (CDF) or Compound File Binary Format (CFBF) document.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.poi:poi`	all versions	3.10-beta1`org.apache.poi:poi:3.10-beta1`
☕Maven	`org.apache.poi:poi-scratchpad`	all versions	3.10-beta1`org.apache.poi:poi-scratchpad:3.10-beta1`

Affected Products

1 product · 60 configurations

Application

poiapache

≤ 3.8

34 versions

0.10.20.30.40.50.60.70.10.00.11.00.12.00.13.00.14.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.poi:poi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.poi:poi to 3.10-beta1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-0213 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.

Red HatModerate

RHSA-2012:1232Red Hat JBoss Portal 5.2