NginxWeb server / proxy · F5
CVE-2022-41741
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedNGINX Open Source before versions 1.23.2 and 1.22.1, NGINX Open Source Subscription before versions R2 P1 and R1 P1, and NGINX Plus before versions R27 P1 and R26 P1 have a vulnerability in the module ngx_http_mp4_module that might allow a local attacker to corrupt NGINX worker memory, resulting in its termination or potential other impact using a specially crafted audio or video file. The issue affects only NGINX products that are built with the ngx_http_mp4_module, when the mp4 directive is used in the configuration file. Further, the attack is possible only if an attacker can trigger processing of a specially crafted audio or video file with the module ngx_http_mp4_module.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA memory corruption vulnerability in NGINX's ngx_http_mp4_module allows a local attacker to corrupt worker process memory by tricking NGINX into processing a specially crafted MP4 file, potentially causing worker crashes or other undefined behavior.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
NginxWeb server / proxy
>= 1.1.3, <= 1.22.0>= r22, <= r27= 1.23.0= 1.23.1= r1= r2
Nginx Ingress ControllerWeb server / proxy
>= 1.9.0, <= 1.12.4>= 2.0.0, <= 2.4.0
FedoraOperating system
= 35= 36= 37
Debian LinuxOperating system
= 10.0= 11.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify ngx_http_mp4_module is compiled into NGINXRun 'nginx -V 2>&1 | grep -o mp4' or check the output of 'nginx -V' for '--with-http_mp4_module' in the configure argumentsAffected if The mp4 module is present in the NGINX build (vulnerable if version is in affected range)
-
Check installed NGINX versionRun 'nginx -v' or 'nginx -V' to obtain the exact version numberAffected if Version is >= 1.1.3 and <= 1.22.0, or equals 1.23.0 or 1.23.1, or falls within r22-r27, r1, or r2
-
Verify if mp4 module is loaded as dynamic moduleCheck for 'load_module modules/ngx_http_mp4_module.so;' in nginx.conf or included configuration files under /etc/nginx/Affected if The dynamic mp4 module is loaded (vulnerable if version is in affected range)
-
Check if mp4 directive is used in configurationSearch configuration files for 'mp4' directive: 'grep -r "mp4" /etc/nginx/' or review each server/location block for 'mp4;' directiveAffected if The 'mp4' directive is enabled in any location block (indicates active attack surface)
-
Confirm MP4 files are being servedReview configuration for location blocks serving .mp4 files, or check access logs for requests to .mp4 endpointsAffected if NGINX is configured to serve or process MP4 files, making the vulnerability exploitable in practice
You are affected if NGINX has the mp4 module compiled or loaded AND its version falls within the affected ranges AND the mp4 directive is enabled in your configuration to serve MP4 content.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade NGINX to version 1.23.2+/1.22.1+ (Open Source) or R27 P1+/R26 P1+ (Plus), or disable the mp4 directive if the module is not required.
NGINX Open Source: upgrade to 1.23.2 or 1.22.1; NGINX Plus: upgrade to R27 P1 or R26 P1; Nginx Ingress Controller: upgrade to 1.12.5+ or 2.4.1+
- Identify the current nginx version installed using 'nginx -v' or 'nginx -V'
- Check if ngx_http_mp4_module is enabled and the mp4 directive is in use in the nginx configuration files (typically in /etc/nginx/ or /usr/local/nginx/conf/)
- If the mp4 module is in use, upgrade nginx to version 1.23.2 (for the mainline) or 1.22.1 (for the stable branch) for NGINX Open Source
- For NGINX Plus subscribers, upgrade to R27 P1 or R26 P1 respectively
- For Nginx Ingress Controller users, upgrade to version 1.12.5 or later for the 1.x branch, or version 2.4.1 or later for the 2.x branch (check vendor documentation for exact fixed versions)
- After upgrade, verify the new version is running with 'nginx -v'
- Test that nginx configuration is valid with 'nginx -t' before reloading
- Reload or restart nginx to apply the changes
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Nginx
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41741 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-41741 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data