{"answers":{"affected":"1 open source package ship an affected version, including contour. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-15127 in the wild and no public exploit code.","fix":"Upgrade contour to 1.7.0 or later.","what":"CVE-2020-15127 is a high-severity missing authorization vulnerability in projectcontour contour, published on 5 Aug 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-15127 and fix it if it is affected.\n\nWhat it is: CVE-2020-15127 is a high-severity missing authorization vulnerability in projectcontour contour, published on 5 Aug 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-15127 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- contour (Bitnami): affected all versions; fixed in 1.7.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-2020-15127/ (Markdown: https://insights.sbomify.com/CVE-2020-15127/index.md)","id":"CVE-2020-15127","markdown":"https://insights.sbomify.com/CVE-2020-15127/index.md","name":"CVE-2020-15127","record":{"aliases":["BIT-contour-2020-15127","GHSA-mjp8-x484-pm3r"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Kubernetes ingress controller","requires_auth":"none","summary":"An unauthenticated attacker can shut down all Envoy instances via an exposed endpoint, causing a complete ingress data plane outage.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"contour","vendor":"projectcontour"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"In Contour ( Ingress controller for Kubernetes) before version 1.7.0, a bad actor can shut down all instances of Envoy, essentially killing the entire ingress data plane. GET requests to /shutdown on port 8090 of the Envoy pod initiate Envoy's shutdown procedure. The shutdown procedure includes flipping the readiness endpoint to false, which removes Envoy from the routing pool. When running Envoy (For example on the host network, pod spec hostNetwork=true), the shutdown manager's endpoint is accessible to anyone on the network that can reach the Kubernetes node that's running Envoy. There is no authentication in place that prevents a rogue actor on the network from shutting down Envoy via the shutdown manager endpoint. Successful exploitation of this issue will lead to bad actors shutting down all instances of Envoy, essentially killing the entire ingress data plane. This is fixed in version 1.7.0.","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":"Denial of service in Contour","id":"CVE-2020-15127","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"missing_authorization","year":"2020"},"n_packages":1,"n_references":2,"next":{"headline":"Reliance on Cookies without validation in OctoberCMS","id":"CVE-2020-15128"},"packages":[{"ecosystem":"Bitnami","fixed":["1.7.0"],"introduced":["0"],"last_affected":[],"package":"contour","purl":"pkg:bitnami/contour","source":"BIT-contour-2020-15127"}],"prev":{"headline":"Information disclosure through Viewer query in parse-server","id":"CVE-2020-15126"},"products":["contour"],"published":"2020-08-05","related":[{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2024-36539","kev_date_added":null,"published":"2024-07-24"},{"cvss_score":8.5,"headline":"Authorization bypass in Contour","id":"CVE-2021-32783","kev_date_added":null,"published":"2021-07-23"},{"cvss_score":8.1,"headline":"Contour: Lua code injection via Cookie Path Rewrite Policy","id":"CVE-2026-41246","kev_date_added":null,"published":"2026-04-23"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["projectcontour"]},"summary":"An unauthenticated attacker can shut down all Envoy instances via an exposed endpoint, causing a complete ingress data plane outage.","url":"https://insights.sbomify.com/CVE-2020-15127/"}