# CVE-2012-1108: Denial of service in n/a

> Remote attackers can crash applications using TagLib by providing a crafted OGG file with a malformed vendorLength field.

- **Severity:** Medium 4.3 (`AV:N/AC:M/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 6 Sep 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-1108, GHSA-3gr9-x3xp-765c

## What is CVE-2012-1108?

CVE-2012-1108 is a medium-severity denial of service vulnerability in n/a, published on 6 Sep 2012. 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

The parse function in ogg/xiphcomment.cpp in TagLib 1.7 and earlier allows remote attackers to cause a denial of service (crash) via a crafted vendorLength field in an ogg file.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2012-1108?

It affects 1 product.


Products: Scott Wheeler Taglib.

## How do I fix CVE-2012-1108?

Upgrade to a fixed version.

## Is CVE-2012-1108 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-1107](https://insights.sbomify.com/CVE-2012-1107/): Denial of service in n/a (medium 4.3)
- [CVE-2012-1584](https://insights.sbomify.com/CVE-2012-1584/): Integer overflow in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-1108 and fix it if it is affected.

What it is: CVE-2012-1108 is a medium-severity denial of service vulnerability in n/a, published on 6 Sep 2012. 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-2012-1108 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-2012-1108/ (Markdown: https://insights.sbomify.com/CVE-2012-1108/index.md)
```

## Sources

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

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