# CVE-2012-1584: Integer overflow in n/a

> An integer overflow in TagLib allows attackers to cause a denial of service via a crafted media file, impacting applications using the library.

- **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:** Not stated
- **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-1584, GHSA-cv7h-2qqx-2rrp

## What is CVE-2012-1584?

CVE-2012-1584 is a medium-severity vulnerability in n/a, published on 6 Sep 2012. 

### Official description

Integer overflow in the mid function in toolkit/tbytevector.cpp in TagLib 1.7 and earlier allows context-dependent attackers to cause a denial of service (application crash) via a crafted file header field in a media file, which triggers a large memory allocation.

Weakness: CWE-189

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

It affects 1 product.


Products: Scott Wheeler Taglib.

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

Upgrade to a fixed version.

## Is CVE-2012-1584 being exploited?

There is no known exploitation of CVE-2012-1584 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-1108](https://insights.sbomify.com/CVE-2012-1108/): Denial of service in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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