# CVE-2011-1931: Memory corruption in n/a

> Remote attackers can execute arbitrary code or cause denial of service via malformed AMV files due to out-of-bounds write in FFmpeg's SP5X decoder.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/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:** No
- **Published:** 7 Jul 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-g323-87f6-pv6c

## What is CVE-2011-1931?

CVE-2011-1931 is a medium-severity memory corruption vulnerability in Ffmpeg Ffmpeg, published on 7 Jul 2011. 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

sp5xdec.c in the Sunplus SP5X JPEG decoder in libavcodec in FFmpeg before 0.6.3 and libav through 0.6.2, as used in VideoLAN VLC media player 1.1.9 and earlier and other products, performs a write operation outside the bounds of an unspecified array, which allows remote attackers to cause a denial of service (memory corruption) or possibly execute arbitrary code via a malformed AMV file.

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

## Which versions are affected by CVE-2011-1931?

It affects 3 products.


Products: Ffmpeg Ffmpeg, Libav Libav, Videolan Vlc Media Player.

## How do I fix CVE-2011-1931?

No fix has been published for CVE-2011-1931 yet. Limit exposure of the affected software until one is available.

## Is CVE-2011-1931 being exploited?

There is no known exploitation of CVE-2011-1931 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-2011-1931 and fix it if it is affected.

What it is: CVE-2011-1931 is a medium-severity memory corruption vulnerability in Ffmpeg Ffmpeg, published on 7 Jul 2011. 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-2011-1931 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-2011-1931/ (Markdown: https://insights.sbomify.com/CVE-2011-1931/index.md)
```

## Sources

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

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