# CVE-2023-6602: Ffmpeg: improper handling of input format in tty demuxer of ffmpeg

> An attacker can exfiltrate data by providing malicious non-TTY-compliant input files to FFmpeg's TTY demuxer during HLS playlist processing.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Dec 2024
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2023-6602, GHSA-398c-f7w9-crc8, JLSEC-2025-142, UBUNTU-CVE-2023-6602

## What is CVE-2023-6602?

CVE-2023-6602 is a medium-severity vulnerability in Ffmpeg Ffmpeg, published on 31 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in FFmpeg's TTY Demuxer. This vulnerability allows possible data exfiltration via improper parsing of non-TTY-compliant input files in HLS playlists.

Weakness: CWE-99 (Improper Control of Resource Identifiers)

## Which versions are affected by CVE-2023-6602?

It affects 1 product.


Products: Ffmpeg Ffmpeg.

## How do I fix CVE-2023-6602?

Upgrade to a fixed version.

## Is CVE-2023-6602 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-6602 exists.

## 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-2023-6602 and fix it if it is affected.

What it is: CVE-2023-6602 is a medium-severity vulnerability in Ffmpeg Ffmpeg, published on 31 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-6602 exists.

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-2023-6602/ (Markdown: https://insights.sbomify.com/CVE-2023-6602/index.md)
```

## Sources

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

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