CVE-2024-7347 | NGINX MP4 module vulnerability

NGINX Open Source and NGINX Plus have a vulnerability in the ngx_http_mp4_module, which might allow an attacker to over-read NGINX worker memory resulting in its termination, using a specially crafted mp4 file. The issue only affects NGINX if it is built with the ngx_http_mp4_module and the mp4 directive is used in the configuration file. Additionally, the attack is possible only if an attacker can trigger the processing of a specially crafted mp4 file with the ngx_http_mp4_module.  Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Published: 2024-08-14 Last update: 2025-11-03 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-7347 is rated Low Risk (31.2/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.32%). 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-7347

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.20% 0.32% +0.12%
2 2026-03-04 0.13% 0.20% +0.07%
3 2026-03-01 — 0.13% —

Full EPSS history (18 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.7 4.0 MEDIUM
CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X Click to expand
Attack vector (AV:L)
Attacker needs local access on the target system.
Attack complexity (AC:H)
Exploitation depends on constrained or hard-to-reproduce conditions.
Attack requirements (AT:P)
Additional preconditions must be present for exploitation.
Privileges required (PR:L)
Low privileges are required.
User interaction (UI:N)
No user interaction is required.
Vulnerable system confidentiality impact (VC:N)
No confidentiality impact on the vulnerable system.
Vulnerable system integrity impact (VI:N)
No integrity impact on the vulnerable system.
Vulnerable system availability impact (VA:H)
High availability impact on the vulnerable system.
Subsequent system confidentiality impact (SC:N)
No confidentiality impact on subsequent systems.
Subsequent system integrity impact (SI:N)
No integrity impact on subsequent systems.
Subsequent system availability impact (SA:N)
No availability impact on subsequent systems.
Exploit maturity (threat) (E:X)
Not defined: no reliable threat intelligence; scoring assumes the worst case (equivalent to Attacked).
Confidentiality requirement (CR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Integrity requirement (IR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Availability requirement (AR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Modified attack vector (MAV:X)
Not defined: scoring uses the Base Attack Vector (AV).
Modified attack complexity (MAC:X)
Not defined: scoring uses the Base Attack Complexity (AC).
Modified attack requirements (MAT:X)
Not defined: scoring uses the Base Attack Requirements (AT).
Modified privileges required (MPR:X)
Not defined: scoring uses the Base Privileges Required (PR).
Modified user interaction (MUI:X)
Not defined: scoring uses the Base User Interaction (UI).
Modified vulnerable system confidentiality impact (MVC:X)
Not defined: scoring uses the Base VC metric.
Modified vulnerable system integrity impact (MVI:X)
Not defined: scoring uses the Base VI metric.
Modified vulnerable system availability impact (MVA:X)
Not defined: scoring uses the Base VA metric.
Modified subsequent system confidentiality impact (MSC:X)
Not defined: scoring uses the Base SC metric.
Modified subsequent system integrity impact (MSI:X)
Not defined: scoring uses the Base SI metric.
Modified subsequent system availability impact (MSA:X)
Not defined: scoring uses the Base SA metric.
Safety (supplemental) (S:X)
Not evaluated.
Automatable (supplemental) (AU:X)
Not evaluated.
Recovery (supplemental) (R:X)
Not evaluated.
Value density (supplemental) (V:X)
Not evaluated.
Vulnerability response effort (supplemental) (RE:X)
Not evaluated.
Provider urgency (supplemental) (U:X)
Not evaluated.
 — — [email protected]
4.7 3.1 MEDIUM
CVSS:3.1/AV:L/AC:H/PR:L/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:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
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.
 1.0 3.6 [email protected]
4.7 3.1 MEDIUM
CVSS:3.1/AV:L/AC:H/PR:L/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:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
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.
 1.0 3.6 [email protected]

Weakness enumeration for CVE-2024-7347

OS Trackers for CVE-2024-7347

vendor priority summary link
alpine medium CVE-2024-7347: 1 source package rows (nginx); 4 state rows across 4 repos (3.20-main, 3.21-main, 3.22-main, edge-main); fixed 4, open 0. https://security.alpinelinux.org/vuln/CVE-2024-7347
debian not yet assigned CVE-2024-7347 not yet assigned priority: Debian including 1 source packages (nginx), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2024-7347
gentoo low CVE-2024-7347: 1 GLSA(s) (202409-32), 1 atom(s) (www-servers/nginx); latest impact low. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2024-7347
redhat medium — https://access.redhat.com/security/cve/CVE-2024-7347
suse medium CVE-2024-7347 severity moderate: SUSE including 21 source package names (1.1.0-1.1:nginx-1.21.5-150600.10.3.1, 1.21-51.11:nginx-1.21.5-150600.10.3.1, …), 47 product×package rows across 21 product lines (Container private-registry/harbor-nginx, Container private-registry/harbor-portal, … (21 product lines)): Fixed 47. https://www.suse.com/security/cve/CVE-2024-7347/
ubuntu medium CVE-2024-7347 medium priority: Ubuntu including 1 source packages (nginx), 8 status rows across 8 suites (bionic, focal, jammy, noble, oracular, trusty, upstream, xenial): released 7, not-affected 1. https://ubuntu.com/security/CVE-2024-7347

Affected software / configurations for CVE-2024-7347

Vendor Product Version Raw CPE
f5 nginx_open_source >= 1.5.13, < 1.26.2 cpe:2.3:a:f5:nginx_open_source:*:*:*:*:*:*:*:*
f5 nginx_open_source 1.27.0 cpe:2.3:a:f5:nginx_open_source:1.27.0:*:*:*:*:*:*:*
f5 nginx_plus >= r27, < r31 cpe:2.3:a:f5:nginx_plus:*:*:*:*:*:*:*:*
f5 nginx_plus r31 cpe:2.3:a:f5:nginx_plus:r31:-:*:*:*:*:*:*
f5 nginx_plus r31 cpe:2.3:a:f5:nginx_plus:r31:p1:*:*:*:*:*:*
f5 nginx_plus r32 cpe:2.3:a:f5:nginx_plus:r32:-:*:*:*:*:*:*

References for CVE-2024-7347

cvelogic Threat Intelligence