CVE-2024-22861VulnerabilityPublished 27 Jan 2024Updated 29 May 2025

CVE-2024-22861: n/a

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 6.1 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.1

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

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

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: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Jan 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 2026-10-25.

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 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

Upgrade ffmpeg/FFmpeg to 6.1.

Affected software

Product	Affected	Fixed in
GitHubffmpeg/FFmpeg`pkg:github/ffmpeg/FFmpeg`Other threats	Affected <6.1	Fixed in 6.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should take immediate steps to mitigate the risk posed by CVE-2024-22861. First, identify all systems and applications that use FFmpeg, either directly or as part of third-party software stacks. This includes media servers, streaming platforms, video conferencing tools, content management systems, and any custom multimedia processing solutions. Next, update FFmpeg to version n6.1 or later as soon as it becomes available, since this version addresses the integer overflow vulnerability. If immediate patching is not possible, implement network-level protections such as filtering or blocking untrusted multimedia content sources, especially those that can deliver crafted media files to vulnerable systems. Employ application-layer gateways or proxies that can sanitize or validate multimedia inputs before processing. Additionally, monitor logs and system behavior for signs of crashes or abnormal terminations related to multimedia processing. Incorporate FFmpeg vulnerability checks into vulnerability management and patching workflows. For software vendors embedding FFmpeg, ensure they release updated versions promptly and communicate the importance of upgrading to their customers. Finally, consider isolating multimedia processing components in sandboxed or containerized environments to limit the impact of potential DoS attacks.

Description

Integer overflow vulnerability in FFmpeg before n6.1, allows attackers to cause a denial of service (DoS) via the avcodec/osq module.

Impact

For European organizations, the impact of CVE-2024-22861 could be significant, especially for those relying heavily on multimedia processing and streaming services, such as broadcasters, media companies, telecommunications providers, and enterprises using video conferencing solutions. A successful exploitation could cause denial of service, leading to service outages, degraded user experience, and potential operational disruptions. This could affect customer trust and lead to financial losses, particularly for service providers with high availability requirements. Additionally, organizations involved in critical infrastructure or public services that utilize FFmpeg for multimedia handling could face operational risks. Although the vulnerability does not directly compromise data confidentiality or integrity, the availability impact alone can have cascading effects on business continuity. The lack of required privileges or user interaction for exploitation increases the risk, as attackers can remotely trigger the vulnerability simply by delivering malicious media content. Given the widespread use of FFmpeg in various software products and services, the attack surface is broad, and organizations must assess their exposure carefully.

CWE-190Integer Overflow or Wraparound (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
Requirements
Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V5.4.3 (opens in a new tab)
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
Attack patterns
Forced Integer Overflow (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/FFmpeg/FFmpeg/commit/87b8c1081959e45ffdcbabb3d53ac9882ef2b5ce (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Jul 2025, 23:57 UTC

WeaknessesCWE-190

Technical details

References

Community reviews

Related threats