# CVE-2010-4008: Memory corruption in n/a

> A memory corruption flaw in libxml2 allows attackers to cause a denial of service via crafted XML documents, affecting applications using the library.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:N/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:** 16 Nov 2010
- **Updated:** 7 Aug 2024
- **Also known as:** CVE-2010-4200, DEBIAN-CVE-2010-4008, DSA-2128-1, GHSA-472j-j78w-732c

## What is CVE-2010-4008?

CVE-2010-4008 is a medium-severity memory corruption vulnerability in Apache Openoffice, published on 16 Nov 2010. 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

libxml2 before 2.7.8, as used in Google Chrome before 7.0.517.44, Apple Safari 5.0.2 and earlier, and other products, reads from invalid memory locations during processing of malformed XPath expressions, which allows context-dependent attackers to cause a denial of service (application crash) via a crafted XML document.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2010-4008?

It affects 15 products.


Products: Apache Openoffice, Apple Iphone Os, Apple Itunes, Apple Mac Os X, Apple Safari, Canonical Ubuntu Linux, Debian Debian Linux, Google Chrome, Opensuse Opensuse, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Eus, Redhat Enterprise Linux Workstation, Suse Suse Linux Enterprise Server, Xmlsoft Libxml2.

## How do I fix CVE-2010-4008?

Upgrade to a fixed version.

## Is CVE-2010-4008 being exploited?

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

## Other vulnerabilities in Apache Openoffice

- [CVE-2014-3524](https://insights.sbomify.com/CVE-2014-3524/): Command injection in n/a (critical 9.3)
- [CVE-2010-3450](https://insights.sbomify.com/CVE-2010-3450/): Path traversal in n/a (critical 9.3)
- [CVE-2010-3451](https://insights.sbomify.com/CVE-2010-3451/): Use after free in n/a (critical 9.3)
- [CVE-2010-3452](https://insights.sbomify.com/CVE-2010-3452/): Use after free in n/a (critical 9.3)
- [CVE-2010-3453](https://insights.sbomify.com/CVE-2010-3453/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-4008 and fix it if it is affected.

What it is: CVE-2010-4008 is a medium-severity memory corruption vulnerability in Apache Openoffice, published on 16 Nov 2010. 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-2010-4008 in the wild and no public exploit code.

Affected product: Apache Openoffice. 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-2010-4008/ (Markdown: https://insights.sbomify.com/CVE-2010-4008/index.md)
```

## Sources

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

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