# CVE-2012-2778: Unspecified vulnerability in FFmpeg before 0.10.3 has unknown impact and attack vectors, a different vulnerability than CVE-2012-2771, CVE-2


- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 9 Aug 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-2778, GHSA-58p7-m454-577v

## What is CVE-2012-2778?

CVE-2012-2778 is a critical vulnerability in Ffmpeg Ffmpeg, published on 9 Aug 2017. 

### Official description

Unspecified vulnerability in FFmpeg before 0.10.3 has unknown impact and attack vectors, a different vulnerability than CVE-2012-2771, CVE-2012-2773, CVE-2012-2780, and CVE-2012-2781.

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

It affects 1 product.


Products: Ffmpeg Ffmpeg.

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

Upgrade to a fixed version.

## Is CVE-2012-2778 being exploited?

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

## Other vulnerabilities in Ffmpeg Ffmpeg

- [CVE-2013-0864](https://insights.sbomify.com/CVE-2013-0864/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-0872](https://insights.sbomify.com/CVE-2013-0872/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-0873](https://insights.sbomify.com/CVE-2013-0873/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-4265](https://insights.sbomify.com/CVE-2013-4265/): Null dereference in n/a (critical 10.0)
- [CVE-2011-3937](https://insights.sbomify.com/CVE-2011-3937/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-2778 is a critical vulnerability in Ffmpeg Ffmpeg, published on 9 Aug 2017. 
Exploitation: There is no known exploitation of CVE-2012-2778 in the wild and no public exploit code.

Affected product: Ffmpeg Ffmpeg. 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-2778/ (Markdown: https://insights.sbomify.com/CVE-2012-2778/index.md)
```

## Sources

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

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