CVE-2012-0213: Medium severity apache poi vulnerability

Published Mar 1, 2012
·
Updated

A flaw was found in the way Apache POI, the Java API for Microsoft Office file formats, handles memory when processing certain Channel Definition Format (CDF) / Compound File Binary Format (CFBF) documents. Apache POI allocates arrays with arbitrary sizes specified in the document. A remote attacker could exploit this flaw by providing a specially-crafted CDF / CFBF file to an application using Apache POI, leading to an to OutOfMemoryError exception in the current thread, or potentially destabilization of the whole Java Virtual Machine instance.

Other sources

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 Software

62 affected componentsFixes available
Apache POI<=3.8
Apache POI=0.1
Apache POI=0.2
Apache POI=0.3
Apache POI=0.4
Apache POI=0.5
Apache POI=0.6
Apache POI=0.7
Apache POI=0.10.0
Apache POI=0.11.0
Apache POI=0.12.0
Apache POI=0.13.0
Apache POI=0.14.0
Apache POI=1.0.0
Apache POI=1.0.1
Apache POI=1.0.2
Apache POI=1.1.0
Apache POI=1.2.0
Apache POI=1.5
Apache POI=1.5.1
Apache POI=1.7-dev
Apache POI=1.8-dev
Apache POI=1.10-dev
Apache POI=2.0
Apache POI=2.0-pre1
Apache POI=2.0-pre2
Apache POI=2.0-pre3
Apache POI=2.0-rc1
Apache POI=2.0-rc2
Apache POI=2.5
Apache POI=2.5.1
Apache POI=3.0
Apache POI=3.0-alpha1
Apache POI=3.0-alpha2
Apache POI=3.0-alpha3
Apache POI=3.0.1
Apache POI=3.0.2
Apache POI=3.0.2-beta1
Apache POI=3.0.2-beta2
Apache POI=3.1
Apache POI=3.1-beta1
Apache POI=3.1-beta2
Apache POI=3.2
Apache POI=3.5
Apache POI=3.5-beta1
Apache POI=3.5-beta2
Apache POI=3.5-beta3
Apache POI=3.5-beta4
Apache POI=3.5-beta5
Apache POI=3.5-beta6
Apache POI=3.6
Apache POI=3.7
Apache POI=3.7-beta1
Apache POI=3.7-beta2
Apache POI=3.7-beta3
Apache POI=3.8-beta1
Apache POI=3.8-beta2
Apache POI=3.8-beta3
Apache POI=3.8-beta4
Apache POI=3.8-beta5
maven/org.apache.poi:poi-scratchpad<3.10-beta1
3.10-beta1
maven/org.apache.poi:poi<3.10-beta1
3.10-beta1

Event History

Mar 1, 2012
Data Sourced
via Red Hat·06:10 PM
DescriptionSeverityAffected Software
Aug 7, 2012
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
Description
May 4, 2022
Advisory Published
via GitHub·12:28 AM

Frequently Asked Questions

1

What is the severity of CVE-2012-0213?

CVE-2012-0213 has a medium severity rating, making it a notable concern for affected users.

2

How do I fix CVE-2012-0213?

To mitigate CVE-2012-0213, upgrade to Apache POI version 3.10-beta1 or later.

3

Which versions of Apache POI are affected by CVE-2012-0213?

CVE-2012-0213 affects Apache POI versions from 0.1 up to and including 3.8.

4

What type of vulnerability is CVE-2012-0213?

CVE-2012-0213 is a memory handling flaw that can lead to potential information disclosure.

5

Can CVE-2012-0213 be exploited remotely?

Yes, CVE-2012-0213 can be exploited remotely by attackers through specially crafted documents.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203