# CVE-2008-2109: Denial of service in n/a

> A denial of service vulnerability in libid3tag allows attackers to cause CPU exhaustion via a malformed ID3 field, impacting applications using this library.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 May 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-2109, GHSA-g6w7-h383-7xgq, openSUSE-SU-2024:10454-1

## What is CVE-2008-2109?

CVE-2008-2109 is a medium-severity denial of service vulnerability in n/a, published on 7 May 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

field.c in the libid3tag 0.15.0b library allows context-dependent attackers to cause a denial of service (CPU consumption) via an ID3_FIELD_TYPE_STRINGLIST field that ends in '\0', which triggers an infinite loop.

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

It affects 1 product.


Products: Media-Libs Libid3tag.

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

Upgrade to a fixed version.

## Is CVE-2008-2109 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2008-2109 is a medium-severity denial of service vulnerability in n/a, published on 7 May 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-2109 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-2109/ (Markdown: https://insights.sbomify.com/CVE-2008-2109/index.md)
```

## Sources

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

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