CVE-2020-15127
Last modified
CVE-2020-15127 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. 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. EPSS estimates a 1.38% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Projectcontour | Contour | < 1.7.0 |
References
- https://github.com/projectcontour/contour/releases/tag/v1.7.0Release Notes, Third Party Advisory
- https://github.com/projectcontour/contour/security/advisories/GHSA-mjp8-x484-pm3rPatch, Third Party Advisory
- https://github.com/projectcontour/contour/releases/tag/v1.7.0Release Notes, Third Party Advisory
- https://github.com/projectcontour/contour/security/advisories/GHSA-mjp8-x484-pm3rPatch, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2020-15127?
How severe is CVE-2020-15127?
How do I fix CVE-2020-15127?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2020
- CVE-2020-15120In "I hate money" before version 4.1.5, an authenticated mem…4.9
- CVE-2020-15121In radare2 before version 4.5.0, malformed PDB file names in…9.6
- CVE-2020-15123In codecov (npm package) before version 3.7.1 the upload met…9.3
- CVE-2020-15124In Goobi Viewer Core before version 4.8.3, a path traversal …6.5
- CVE-2020-15125In auth0 (npm package) versions before 2.27.1, a DenyList of…7.7
- CVE-2020-15126In parser-server from version 3.5.0 and before 4.3.0, an aut…6.5
- CVE-2020-15128In OctoberCMS before version 1.0.468, encrypted cookie value…6.3
- CVE-2020-15129In Traefik before versions 1.7.26, 2.2.8, and 2.3.0-rc3, the…4.7
- CVE-2020-1513An elevation of privilege vulnerability exists when the Wind…7.8
- CVE-2020-15130In SLPJS (npm package slpjs) before version 0.27.4, there is…7.5
- CVE-2020-15131In SLP Validate (npm package slp-validate) before version 1.…7.5
- CVE-2020-15132In Sulu before versions 1.6.35, 2.0.10, and 2.1.1, when the …5.3
Are you affected by CVE-2020-15127?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
