# CVE-2009-0136: Memory corruption in n/a

> Remote attackers can execute arbitrary code or crash Amarok by tricking users into opening a malicious Audible audio file.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **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 Jan 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-0136, GHSA-v2j5-6pgm-rh74

## What is CVE-2009-0136?

CVE-2009-0136 is a critical memory corruption vulnerability in n/a, published on 16 Jan 2009. 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

Multiple array index errors in the Audible::Tag::readTag function in metadata/audible/audibletag.cpp in Amarok 1.4.10 through 2.0.1 allow remote attackers to cause a denial of service (application crash) or execute arbitrary code via an Audible Audio (.aa) file with a crafted (1) nlen or (2) vlen Tag value, each of which can lead to an invalid pointer dereference, or the writing of a 0x00 byte to an arbitrary memory location, after an allocation failure.

Weakness: CWE-189

## Which versions are affected by CVE-2009-0136?

It affects 1 product.


Products: Amarok Amarok.

## How do I fix CVE-2009-0136?

Upgrade to a fixed version.

## Is CVE-2009-0136 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-0135](https://insights.sbomify.com/CVE-2009-0135/): Integer overflow in n/a (critical 9.3)
- [CVE-2006-6979](https://insights.sbomify.com/CVE-2006-6979/): Command injection in n/a (high 7.5)
- [CVE-2008-3699](https://insights.sbomify.com/CVE-2008-3699/): Path traversal in n/a (low 3.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-0136 and fix it if it is affected.

What it is: CVE-2009-0136 is a critical memory corruption vulnerability in n/a, published on 16 Jan 2009. 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-2009-0136 in the wild and no public exploit code.

Affected product: n/a. 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-2009-0136/ (Markdown: https://insights.sbomify.com/CVE-2009-0136/index.md)
```

## Sources

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

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