CVE-2024-36618

FFmpeg n6.1.1 has a vulnerability in the AVI demuxer of the libavformat library which allows for an integer overflow, potentially resulting in a denial-of-service (DoS) condition.

Published: 2024-11-29 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-36618 is rated Low Risk (30.1/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.24%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-36618

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.04% 0.24% +0.20%
2 2026-01-07 0.06% 0.04% -0.02%
3 2025-10-20 — 0.06% —

Full EPSS history (12 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-36618

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.2 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.5 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-36618

OS Trackers for CVE-2024-36618

vendor priority summary link
debian not yet assigned CVE-2024-36618 not yet assigned priority: Debian including 1 source packages (ffmpeg), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2024-36618
suse medium CVE-2024-36618 severity moderate: SUSE including 146 source package names (0.3.2-1.2:libavcodec58_134-4.4.6-150600.13.27.1, 0.3.2-1.2:libavformat58_76-4.4.6-150600.13.27.1, …), 286 product×package rows across 22 product lines (Container containers/lmcache-vllm-openai, Container containers/open-webui, … (22 product lines)): Fixed 286. https://www.suse.com/security/cve/CVE-2024-36618/
ubuntu medium CVE-2024-36618 medium priority: Ubuntu including 2 source packages (ffmpeg, libav), 17 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 6, released 6, not-affected 3, needs-triage 2. https://ubuntu.com/security/CVE-2024-36618

Affected software / configurations for CVE-2024-36618

Vendor Product Version Raw CPE
ffmpeg ffmpeg 6.1.1 cpe:2.3:a:ffmpeg:ffmpeg:6.1.1:*:*:*:*:*:*:*

References for CVE-2024-36618

cvelogic Threat Intelligence