# CVE-2017-14056: Denial of service in n/a

> A crafted RL2 file causes excessive CPU and memory consumption in FFmpeg due to missing EOF checks, leading to denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **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:** 31 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2017-14056, CLEANSTART-2024-MI06720, DEBIAN-CVE-2017-14056, GHSA-r5h2-24x5-fv2h, UBUNTU-CVE-2017-14056

## What is CVE-2017-14056?

CVE-2017-14056 is a medium-severity denial of service vulnerability in Ffmpeg Ffmpeg, published on 31 Aug 2017. 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

In libavformat/rl2.c in FFmpeg 3.3.3, a DoS in rl2_read_header() due to lack of an EOF (End of File) check might cause huge CPU and memory consumption. When a crafted RL2 file, which claims a large "frame_count" field in the header but does not contain sufficient backing data, is provided, the loops (for offset and size tables) would consume huge CPU and memory resources, since there is no EOF check inside these loops.

Weakness: CWE-834 (Excessive Iteration)

## Which versions are affected by CVE-2017-14056?

It affects 1 product.


Products: Ffmpeg Ffmpeg.

## How do I fix CVE-2017-14056?

Upgrade to a fixed version.

## Is CVE-2017-14056 being exploited?

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

What it is: CVE-2017-14056 is a medium-severity denial of service vulnerability in Ffmpeg Ffmpeg, published on 31 Aug 2017. 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-2017-14056 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-2017-14056/ (Markdown: https://insights.sbomify.com/CVE-2017-14056/index.md)
```

## Sources

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

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