# CVE-2007-6277: Memory corruption in n/a

> Remote attackers can execute arbitrary code by tricking users into opening malicious FLAC files with vulnerable libFLAC versions.

- **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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 7 Dec 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-6277, GHSA-5955-gqmh-73gj

## What is CVE-2007-6277?

CVE-2007-6277 is a critical memory corruption vulnerability in n/a, published on 7 Dec 2007. 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

Multiple buffer overflows in Free Lossless Audio Codec (FLAC) libFLAC before 1.2.1 allow user-assisted remote attackers to execute arbitrary code via large (1) Metadata Block Size, (2) VORBIS Comment String Size, (3) Picture Metadata MIME-TYPE Size, (4) Picture Description Size, (5) Picture Data Length, (6) Padding Length, and (7) PICTURE Metadata width and height values in a .FLAC file, which result in a heap-based overflow; and large (8) VORBIS Comment String Size Length, (9) Picture MIME-Type, (10) Picture MIME-Type URL, and (11) Picture Description Length values in a .FLAC file, which result in a stack-based overflow.  NOTE: some of these issues may overlap CVE-2007-4619.

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

## Which versions are affected by CVE-2007-6277?

It affects 1 product.


Products: Flac Libflac.

## How do I fix CVE-2007-6277?

Upgrade to a fixed version.

## Is CVE-2007-6277 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-6278](https://insights.sbomify.com/CVE-2007-6278/): Other in n/a (critical 9.3)
- [CVE-2007-6279](https://insights.sbomify.com/CVE-2007-6279/): Use after free in n/a (critical 9.3)
- [CVE-2007-4619](https://insights.sbomify.com/CVE-2007-4619/): Integer overflow in n/a (critical 9.3)
- [CVE-2014-8962](https://insights.sbomify.com/CVE-2014-8962/): Memory corruption in n/a (high 7.5)
- [CVE-2014-9028](https://insights.sbomify.com/CVE-2014-9028/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-6277 and fix it if it is affected.

What it is: CVE-2007-6277 is a critical memory corruption vulnerability in n/a, published on 7 Dec 2007. 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-2007-6277 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-2007-6277/ (Markdown: https://insights.sbomify.com/CVE-2007-6277/index.md)
```

## Sources

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

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