# CVE-2022-41743: NGINX ngx_http_hls_module vulnerability CVE-2022-41743

> A local attacker can corrupt NGINX worker memory via crafted media files, causing crashes or potential code execution in NGINX Plus with HLS enabled.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Oct 2022
- **Updated:** 8 May 2025
- **Also known as:** BIT-nginx-ingress-controller-2022-41743, GHSA-g286-fgpf-9wp8

## What is CVE-2022-41743?

CVE-2022-41743 is a high-severity memory corruption vulnerability in F5 NGINX Plus, published on 19 Oct 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2022-41743?

1 open source package ship an affected version, including nginx-ingress-controller. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nginx-ingress-controller` | Bitnami | From 1.9.0 | 1.12.4, 2.4.0 |

Products: F5 Nginx Ingress Controller, F5 Nginx Plus.

## How do I fix CVE-2022-41743?

Upgrade nginx-ingress-controller to a fixed version for your release line: 1.12.4 or 2.4.0.

## Is CVE-2022-41743 being exploited?

There is no known exploitation of CVE-2022-41743 in the wild and no public exploit code.

## Other vulnerabilities in F5 NGINX Plus

- [CVE-2026-55723](https://insights.sbomify.com/CVE-2026-55723/): NGINX Ingress Controller vulnerability (high 8.7)
- [CVE-2025-14727](https://insights.sbomify.com/CVE-2025-14727/): NGINX Ingress Controller vulnerability (high 8.7)
- [CVE-2026-52865](https://insights.sbomify.com/CVE-2026-52865/): NGINX Ingress Controller vulnerability (high 7.1)
- [CVE-2022-30535](https://insights.sbomify.com/CVE-2022-30535/): NGINX Ingress Controller vulnerability CVE-2022-30535 (medium 6.5)
- [CVE-2021-23055](https://insights.sbomify.com/CVE-2021-23055/): Security feature bypass in NGINX Ingress Controller (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41743 and fix it if it is affected.

What it is: CVE-2022-41743 is a high-severity memory corruption vulnerability in F5 NGINX Plus, published on 19 Oct 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-41743 in the wild and no public exploit code.

Affected packages and fixed versions:
- nginx-ingress-controller (Bitnami): affected from 1.9.0; fixed in 1.12.4, 2.4.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-41743/ (Markdown: https://insights.sbomify.com/CVE-2022-41743/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-41743
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-41743
- OSV: https://osv.dev/vulnerability/CVE-2022-41743

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-41743/
Summaries are generated and may contain mistakes; the official description above is the record.