VulnerabilityPublished 31 Dec 2024Updated 3 Nov 2025

CVE-2023-6602: Resource Injection

Source CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 31 Dec 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2023-6602, European organizations should implement the following specific measures: 1) Immediately audit and inventory all FFmpeg deployments, focusing on version 2.0 and usage in HLS playlist processing. 2) Restrict ingestion of HLS playlists to trusted sources only, employing network-level filtering and application whitelisting to prevent malicious inputs. 3) Implement input validation and sanitization at the application layer before passing playlists to FFmpeg, ensuring non-TTY-compliant or malformed inputs are rejected. 4) Monitor network traffic for unusual outbound data flows that could indicate exfiltration attempts via media streams. 5) Deploy intrusion detection systems (IDS) with signatures tuned to detect anomalies in HLS playlist handling. 6) Stay updated with FFmpeg project releases and apply patches promptly once available. 7) Consider isolating media processing workloads in sandboxed or containerized environments to limit exposure. 8) Conduct regular security assessments and penetration testing focused on media streaming components to identify potential exploitation paths. These targeted steps go beyond generic advice by focusing on the specific attack vector and operational context of the vulnerability.

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.

Impact

For European organizations, the primary impact of CVE-2023-6602 is the potential unauthorized disclosure of sensitive data through crafted HLS playlists processed by vulnerable FFmpeg instances. This can compromise confidentiality without affecting system integrity or availability. Organizations involved in media streaming, broadcasting, or content delivery networks that utilize FFmpeg for handling HLS streams are at heightened risk. Data exfiltration could lead to leakage of proprietary media content, user data, or internal system information, potentially resulting in reputational damage and regulatory compliance issues under GDPR. Since exploitation requires no authentication or user interaction, attackers can remotely target exposed media processing infrastructure. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially as threat actors may develop exploits over time. The impact is more pronounced in sectors with high media content turnover and streaming reliance, including broadcasters, OTT platforms, and media service providers across Europe.

References

Community reviews

Loading reviews…