CVE-2020-8561 Lets Kubernetes API Server SSRF Reveal Full Responses

Summary
CVE-2020-8561 combines Kubernetes webhook-based SSRF with API server profiling to expose full responses. Exploitation requires valid credentials and elevated permissions; disabling profiling and limiting network access can reduce risk.
Key points
- An attacker with valid Kubernetes credentials and elevated permissions, typically cluster-admin, can change the API server log level through profiling endpoints.
- A crafted ValidatingWebhookConfiguration can make the API server send requests to attacker-specified URLs when matching resources are created or updated.
- Debug-level logging can expose full responses to those SSRF requests, beyond basic port-scanning information.
- The impact may be greater when control-plane nodes are isolated from workers or operate in a cloud provider network, where the API server may reach privileged services.
- The article says there is no simple code fix; mitigations include disabling API server profiling and designing network architecture so SSRF requests provide no advantage.
- Testing the proof of concept could disrupt cluster operation; the article recommends using a dedicated test cluster without other workloads.
Article Details
- Vulnerability Types
- Server-side request forgery (SSRF)
- Information disclosure
- Exploitation Status
- unknown
- Exploit Availability
- public_poc
- Patch Status
- unavailable
- Workarounds
- Set the API server's --profiling flag to false.
- Configure network architecture so SSRF requests from the Kubernetes API server provide no advantage.
