{"answers":{"affected":"2 open source packages ship an affected version, including k8s.io/ingress-nginx. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-5043 in the wild and no public exploit code.","fix":"Upgrade k8s.io/ingress-nginx to 1.9.0 or later.","what":"CVE-2023-5043 is a high-severity command injection vulnerability in Kubernetes ingress-nginx, published on 25 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-5043 and fix it if it is affected.\n\nWhat it is: CVE-2023-5043 is a high-severity command injection vulnerability in Kubernetes ingress-nginx, published on 25 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-5043 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- k8s.io/ingress-nginx (Go): affected all versions; fixed in 1.9.0\n- k8s.io/ingress-nginx (Go): affected all versions; fixed in 1.9.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-2023-5043/ (Markdown: https://insights.sbomify.com/CVE-2023-5043/index.md)","id":"CVE-2023-5043","markdown":"https://insights.sbomify.com/CVE-2023-5043/index.md","name":"CVE-2023-5043","record":{"aliases":["GHSA-5wj4-wffq-3378"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes ingress controller","requires_auth":"low_privilege","summary":"Attackers can inject malicious annotations into Ingress resources to execute arbitrary commands on the ingress-nginx controller.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"kubernetes","cpe":[{"product":"ingress-nginx","vendor":"kubernetes"}],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Ingress nginx annotation injection causes arbitrary command execution.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":"2024-01-15","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2024-01-15T09:20:35Z","kind":"github_poc","ref":"https://github.com/r0binak/CVE-2023-5043","stars":0,"title":"PoC CVE-2023-5043"}],"tier":"poc_unverified"},"has_fix":true,"headline":"Ingress nginx annotation injection causes arbitrary command execution","id":"CVE-2023-5043","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"command_injection","year":"2023"},"n_packages":2,"n_references":4,"next":{"headline":"Code injection via nginx.ingress.kubernetes.io/permanent-redirect annotation","id":"CVE-2023-5044"},"packages":[{"ecosystem":"Go","fixed":["1.9.0"],"introduced":["0"],"last_affected":[],"package":"k8s.io/ingress-nginx","purl":null,"source":"GHSA-5wj4-wffq-3378"},{"ecosystem":"Go","fixed":["1.9.0"],"introduced":["0"],"last_affected":[],"package":"k8s.io/ingress-nginx","purl":"pkg:golang/k8s.io/ingress-nginx","source":"GHSA-5wj4-wffq-3378"}],"prev":{"headline":"Information disclosure in Acronis Cyber Protect Home Office","id":"CVE-2023-5042"},"products":["ingress-nginx"],"published":"2023-10-25","related":[{"cvss_score":8.8,"headline":"ingress-nginx rewrite-target nginx configuration injection","id":"CVE-2026-3288","kev_date_added":null,"published":"2026-03-09"},{"cvss_score":8.8,"headline":"Ingress-nginx `path` sanitization can be bypassed with `log_format` directive","id":"CVE-2022-4886","kev_date_added":null,"published":"2023-10-25"},{"cvss_score":7.6,"headline":"Code injection via nginx.ingress.kubernetes.io/permanent-redirect annotation","id":"CVE-2023-5044","kev_date_added":null,"published":"2023-10-25"},{"cvss_score":7.6,"headline":"Ingress-nginx `path` sanitization can be bypassed with newline character","id":"CVE-2021-25748","kev_date_added":null,"published":"2023-05-24"},{"cvss_score":7.6,"headline":"Ingress-nginx path can be pointed to service account token file","id":"CVE-2021-25745","kev_date_added":null,"published":"2022-05-06"},{"cvss_score":7.6,"headline":"Ingress-nginx directive injection via annotations","id":"CVE-2021-25746","kev_date_added":null,"published":"2022-05-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2025-02-13","vendors":["Kubernetes"]},"summary":"Attackers can inject malicious annotations into Ingress resources to execute arbitrary commands on the ingress-nginx controller.","url":"https://insights.sbomify.com/CVE-2023-5043/"}