# CVE-2006-2458: Libextractor multiple heap-based buffer overflows

> Remote attackers can execute arbitrary code via heap-based buffer overflows in Libextractor's ASF and QT plugins.

- **Severity:** Medium 4.0 (`AV:N/AC:H/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-2458, DSA-1081-1, GHSA-f836-7jqw-3684, PYSEC-2006-4

## What is CVE-2006-2458?

CVE-2006-2458 is a medium-severity memory corruption vulnerability in n/a, published on 18 May 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple heap-based buffer overflows in Libextractor 0.5.13 and earlier allow remote attackers to execute arbitrary code via (1) the asf_read_header function in the ASF plugin (plugins/asfextractor.c), and (2) the parse_trak_atom function in the QT plugin (plugins/qtextractor.c).

## Which versions are affected by CVE-2006-2458?

3 open source packages ship an affected version, including extractor. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `extractor` | PyPI | All versions | None |
| `extractor` | PyPI | All versions | None |
| `extractor` | PyPI | All versions | None |

Products: Libextractor Libextractor.

## How do I fix CVE-2006-2458?

Upgrade to a fixed version.

## Is CVE-2006-2458 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-2458 exists.

Public exploit code:

- libextractor 0.5.13 - Multiple Heap Overflows (PoC) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-2458 and fix it if it is affected.

What it is: CVE-2006-2458 is a medium-severity memory corruption vulnerability in n/a, published on 18 May 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-2458 exists.

Affected packages and fixed versions:
- extractor (PyPI): affected all versions; no fix listed
- extractor (PyPI): affected all versions; no fix listed
- extractor (PyPI): affected all versions; no fix listed

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-2006-2458/ (Markdown: https://insights.sbomify.com/CVE-2006-2458/index.md)
```

## Sources

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

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