dbcve.org
Nginx Ingress ControllerWeb server / proxy · F5

CVE-2022-41743

HIGH · 7.0 CVSS v3.1 Published 2022-10-19
Fix available
A fix is available. Upgrade to after 2.4.0 or later.
See remediation →
72/100
Remediation priority · Elevated
Zero-click

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 · unedited
NGINX Plus before versions R27 P1 and R26 P1 have a vulnerability in the module ngx_http_hls_module that might allow a local attacker to corrupt NGINX worker memory, resulting in its crash or potential other impact using a specially crafted audio or video file. The issue affects only NGINX Plus when the hls 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_hls_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 confidence

Memory corruption vulnerability in NGINX Plus ngx_http_hls_module allows a local attacker to corrupt worker process memory via specially crafted audio/video files, causing crashes or potential further impact. Attack requires triggering HLS module processing of malicious media files.

MitigationUpgrade NGINX Plus to R27 P1 or R26 P1. If upgrade is not feasible, disable the hls directive in the configuration and ensure untrusted media files cannot be processed by the HLS module.

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
Nginx Ingress ControllerWeb server / proxy
Affected:>= 1.9.0, <= 1.12.4>= 2.0.0, <= 2.4.0
Nginx PlusWeb server / proxy
Affected:>= r22, <= r27

CVSS 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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the NGINX Plus version
    Run 'nginx -v' or 'nginx -V' to determine the installed version. For F5 Nginx Plus, look for versions labeled r22 through r27.
    Affected if The version shows r22, r23, r24, r25, r26, or r27 (the r27 label includes all versions up to r27 without P1)
  2. Identify the Nginx Ingress Controller version
    For Kubernetes deployments, run 'kubectl get deployment -n <ingress-namespace> -o jsonpath={.spec.template.spec.containers[0].image}' to retrieve the deployed image tag.
    Affected if The version is 1.9.0 through 1.12.4, or 2.0.0 through 2.4.0
  3. Verify the HLS module is loaded
    Run 'nginx -V 2>&1 | grep -i hls' to list compiled-in modules. The presence of 'ngx_http_hls_module' indicates the module is available.
    Affected if The output contains ngx_http_hls_module, meaning the module is compiled in
  4. Confirm HLS directives are in use
    Search nginx configuration files for 'hls' directives: 'grep -r "hls" /etc/nginx/' or review the main nginx.conf and included files.
    Affected if Configuration contains hls directives (such as hls, hls_buf_size, hls_fragment, hls_ts_fallback, or similar HLS-related settings)
  5. Verify HLS processing is accessible to untrusted sources
    Review the server block configuration where HLS is enabled. Check if the location handling media file requests is accessible without authentication or if untrusted media files can be uploaded and processed.
    Affected if HLS-processed media endpoints are reachable by untrusted users or untrusted media files can be submitted for HLS processing

A system is affected if it runs NGINX Plus r22-r27 or Nginx Ingress Controller 1.9.0-2.4.0, has the HLS module compiled in, has HLS directives configured, and processes untrusted media files through the HLS module.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 2.4.0
Interim mitigation

Upgrade NGINX Plus to R27 P1 or R26 P1. If upgrade is not feasible, disable the hls directive in the configuration and ensure untrusted media files cannot be processed by the HLS module.

Recommended fix Moderate confidence

Nginx Plus: R27 P1 or R26 P1; Nginx Ingress Controller: 2.4.1 or later (latest stable)

  1. For Nginx Plus: Upgrade to R27 P1 or R26 P1 as specified in the F5 support advisory
  2. For Nginx Ingress Controller: Upgrade to a version beyond 2.4.0 (latest stable release recommended)
  3. If upgrade is not immediately possible, consider disabling the hls directive in nginx.conf if not strictly required
  4. Review nginx.conf configuration files to identify any uses of the hls directive
  5. After upgrade, verify that NGINX worker processes restart successfully
Caveat Review configuration compatibility for hls module directives after upgrade; Nginx Ingress Controller major version 3.x may have configuration changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nginx Ingress Controller Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41743 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-41743 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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