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

> Heap-based buffer overflow in libaudiofile allows attackers to execute arbitrary code or cause a crash via a crafted WAV file.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 2 Jan 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-5824, DSA-1972-1, GHSA-wj2h-43mg-5f25

## What is CVE-2008-5824?

CVE-2008-5824 is a medium-severity memory corruption vulnerability in n/a, published on 2 Jan 2009. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Heap-based buffer overflow in msadpcm.c in libaudiofile in audiofile 0.2.6 allows context-dependent attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted WAV file.

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

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

It affects 1 product.


Products: 68k Audiofile.

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

Upgrade to a fixed version.

## Is CVE-2008-5824 being exploited?

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

Public exploit code:

- Audio File Library 0.2.6 - libaudiofile 'msadpcm.c .WAV' File Processing Buffer Overflow (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-5824 is a medium-severity memory corruption vulnerability in n/a, published on 2 Jan 2009. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-5824 exists.

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

## Sources

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

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