{"answers":{"affected":"1 open source package ship an affected version, including nginx-ingress-controller. It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-41743 in the wild and no public exploit code.","fix":"Upgrade nginx-ingress-controller to a fixed version for your release line: 1.12.4 or 2.4.0.","what":"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."},"fix_prompt":"Check this codebase for CVE-2022-41743 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2022-41743 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nginx-ingress-controller (Bitnami): affected from 1.9.0; fixed in 1.12.4, 2.4.0\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-41743/ (Markdown: https://insights.sbomify.com/CVE-2022-41743/index.md)","id":"CVE-2022-41743","markdown":"https://insights.sbomify.com/CVE-2022-41743/index.md","name":"CVE-2022-41743","record":{"aliases":["BIT-nginx-ingress-controller-2022-41743","GHSA-g286-fgpf-9wp8"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"NGINX Plus HLS module","requires_auth":"low_privilege","summary":"A local attacker can corrupt NGINX worker memory via crafted media files, causing crashes or potential code execution in NGINX Plus with HLS enabled.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"f5","cpe":[{"product":"nginx_ingress_controller","vendor":"f5"},{"product":"nginx_plus","vendor":"f5"}],"cvss":{"score":7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"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.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"NGINX ngx_http_hls_module vulnerability CVE-2022-41743","id":"CVE-2022-41743","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":1,"n_references":1,"next":{"headline":"Race condition in Trend Micro Apex One","id":"CVE-2022-41744"},"packages":[{"ecosystem":"Bitnami","fixed":["1.12.4","2.4.0"],"introduced":["1.9.0","2.0.0"],"last_affected":[],"package":"nginx-ingress-controller","purl":"pkg:bitnami/nginx-ingress-controller","source":"BIT-nginx-ingress-controller-2022-41743"}],"prev":{"headline":"NGINX ngx_http_mp4_module vulnerability CVE-2022-41742","id":"CVE-2022-41742"},"products":["NGINX Plus"],"published":"2022-10-19","related":[{"cvss_score":8.7,"headline":"NGINX Ingress Controller vulnerability","id":"CVE-2026-55723","kev_date_added":null,"published":"2026-07-15"},{"cvss_score":8.7,"headline":"NGINX Ingress Controller vulnerability","id":"CVE-2025-14727","kev_date_added":null,"published":"2025-12-17"},{"cvss_score":7.1,"headline":"NGINX Ingress Controller vulnerability","id":"CVE-2026-52865","kev_date_added":null,"published":"2026-07-15"},{"cvss_score":6.5,"headline":"NGINX Ingress Controller vulnerability CVE-2022-30535","id":"CVE-2022-30535","kev_date_added":null,"published":"2022-08-04"},{"cvss_score":6.5,"headline":"Security feature bypass in NGINX Ingress Controller","id":"CVE-2021-23055","kev_date_added":null,"published":"2022-04-21"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-05-08","vendors":["F5"]},"summary":"A local attacker can corrupt NGINX worker memory via crafted media files, causing crashes or potential code execution in NGINX Plus with HLS enabled.","url":"https://insights.sbomify.com/CVE-2022-41743/"}