CVE-2020-15127

Source
https://nvd.nist.gov/vuln/detail/CVE-2020-15127
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2020-15127.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2020-15127
Aliases
Related
  • GHSA-mjp8-x484-pm3r
Published
2020-08-05T21:15:12Z
Modified
2025-01-14T08:42:22.928863Z
Severity
  • 7.5 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
Summary
[none]
Details

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.

References

Affected packages

Git / github.com/projectcontour/contour

Affected ranges

Type
GIT
Repo
https://github.com/projectcontour/contour
Events
Introduced
0 Unknown introduced commit / All previous commits are affected
Fixed

Affected versions

Other

docker-base-layer

v0.*

v0.10.0-rc.1
v0.13.0-beta.1
v0.13.0-beta.2
v0.6.0-alpha.1
v0.6.0-alpha.2
v0.6.0-alpha.3
v0.6.0-beta.1
v0.6.0-beta.2
v0.6.0-beta.3

v1.*

v1.2.0