# CVE-2012-2149: Integer overflow in n/a

> Remote attackers can execute arbitrary code via a crafted WordPerfect document due to an integer overflow in libwpd, affecting OpenOffice.org users.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 21 Jun 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-2149, GHSA-q242-fx58-pm2p, RHSA-2012:1043

## What is CVE-2012-2149?

CVE-2012-2149 is a high-severity vulnerability in Redhat Enterprise Linux Desktop, published on 21 Jun 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The WPXContentListener::_closeTableRow function in WPXContentListener.cpp in libwpd 0.8.8, as used by OpenOffice.org (OOo) before 3.4, allows remote attackers to execute arbitrary code via a crafted Wordperfect .WPD document that causes a negative array index to be used.  NOTE: some sources report this issue as an integer overflow.

Weakness: CWE-189

## Which versions are affected by CVE-2012-2149?

It affects 4 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libwpd` | Red Hat:enterprise_linux:5::client | All versions | 0:0.8.7-3.1.el5_8 |
| `libwpd-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:0.8.7-3.1.el5_8 |
| `libwpd-tools` | Red Hat:enterprise_linux:5::client | All versions | 0:0.8.7-3.1.el5_8 |
| `libwpd` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:0.8.7-3.1.el5_8 |
| `libwpd-debuginfo` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:0.8.7-3.1.el5_8 |
| `libwpd-devel` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:0.8.7-3.1.el5_8 |
| `libwpd` | Red Hat:rhel_productivity:5 | All versions | 0:0.8.7-3.1.el5_8 |
| `libwpd-debuginfo` | Red Hat:rhel_productivity:5 | All versions | 0:0.8.7-3.1.el5_8 |
| `libwpd-devel` | Red Hat:rhel_productivity:5 | All versions | 0:0.8.7-3.1.el5_8 |
| `libwpd-tools` | Red Hat:rhel_productivity:5 | All versions | 0:0.8.7-3.1.el5_8 |

Products: Apache Openoffice.org, Libwpd Libwpd, Redhat Enterprise Linux  Optional Productivity Applications, Redhat Enterprise Linux Desktop.

## How do I fix CVE-2012-2149?

Upgrade to a fixed version.

## Is CVE-2012-2149 being exploited?

There is no known exploitation of CVE-2012-2149 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Enterprise Linux Desktop

- [CVE-2009-3569](https://insights.sbomify.com/CVE-2009-3569/): Memory corruption in n/a (critical 9.3)
- [CVE-2012-1149](https://insights.sbomify.com/CVE-2012-1149/): Integer overflow in n/a (high 7.5)
- [CVE-2012-2334](https://insights.sbomify.com/CVE-2012-2334/): Integer overflow in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-2149 and fix it if it is affected.

What it is: CVE-2012-2149 is a high-severity vulnerability in Redhat Enterprise Linux Desktop, published on 21 Jun 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2012-2149 in the wild and no public exploit code.

Affected product: Redhat Enterprise Linux Desktop. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2012-2149/ (Markdown: https://insights.sbomify.com/CVE-2012-2149/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2012-2149
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-2149
- OSV: https://osv.dev/vulnerability/CVE-2012-2149

---
From sbomify Insights: https://insights.sbomify.com/CVE-2012-2149/
Summaries are generated and may contain mistakes; the official description above is the record.