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

> A buffer overflow in the Secret Rabbit Code library allows attackers to execute arbitrary code or cause denial of service via a crafted audio file when extreme low conversion ratios are used.

- **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:** Not stated
- **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-5008, GHSA-fj55-7h97-pmmv, openSUSE-SU-2024:10987-1

## What is CVE-2008-5008?

CVE-2008-5008 is a critical memory corruption vulnerability in n/a, published on 10 Nov 2008. 

### Official description

Buffer overflow in src/src_sinc.c in Secret Rabbit Code (aka SRC or libsamplerate) before 0.1.4, when "extreme low conversion ratios" are used, allows user-assisted attackers to have an unknown impact via a crafted audio file.

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

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

It affects 1 product.


Products: Mega-Nerd Secret Rabbit Code.

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

Upgrade to a fixed version.

## Is CVE-2008-5008 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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