# CVE-2016-7502: Memory corruption in n/a

> An out-of-bounds read in FFmpeg's CAVS decoder allows attackers to cause denial of service or potentially execute code via crafted media files.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 Dec 2016
- **Updated:** 6 Aug 2024
- **Also known as:** ALPINE-CVE-2016-7502, DEBIAN-CVE-2016-7502, GHSA-v4f4-cvgv-7g4f, UBUNTU-CVE-2016-7502

## What is CVE-2016-7502?

CVE-2016-7502 is a high-severity memory corruption vulnerability in Ffmpeg Ffmpeg, published on 23 Dec 2016. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The cavs_idct8_add_c function in libavcodec/cavsdsp.c in FFmpeg before 3.1.4 is vulnerable to reading out-of-bounds memory when decoding with cavs_decode.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2016-7502?

It affects 1 product.


Products: Ffmpeg Ffmpeg.

## How do I fix CVE-2016-7502?

Upgrade to a fixed version.

## Is CVE-2016-7502 being exploited?

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

What it is: CVE-2016-7502 is a high-severity memory corruption vulnerability in Ffmpeg Ffmpeg, published on 23 Dec 2016. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-7502 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-2016-7502/ (Markdown: https://insights.sbomify.com/CVE-2016-7502/index.md)
```

## Sources

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

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