# CVE-2008-5030: Memory corruption in n/a

> Remote CDDB servers can execute arbitrary code via a heap-based buffer overflow in libcdaudio when a user accesses malicious CD data.

- **Severity:** Critical 10.0 (`AV:N/AC:L/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:** 10 Nov 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-5030, DSA-1665-1, GHSA-6q76-4mmr-j6rw

## What is CVE-2008-5030?

CVE-2008-5030 is a critical memory corruption vulnerability in n/a, published on 10 Nov 2008. 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

Heap-based buffer overflow in the cddb_read_disc_data function in cddb.c in libcdaudio 0.99.12p2 allows remote CDDB servers to execute arbitrary code via long CDDB data.

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

## Which versions are affected by CVE-2008-5030?

It affects 1 product.


Products: Libcaudio Libcaudio.

## How do I fix CVE-2008-5030?

Upgrade to a fixed version.

## Is CVE-2008-5030 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-5030 and fix it if it is affected.

What it is: CVE-2008-5030 is a critical memory corruption vulnerability in n/a, published on 10 Nov 2008. 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-2008-5030 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-2008-5030/ (Markdown: https://insights.sbomify.com/CVE-2008-5030/index.md)
```

## Sources

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

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