CVE-2020-5416 CF clusters with NGINX in front of them may be vulnerable to DoS
Unauthenticated attackers can cause denial of service in Cloud Foundry deployments using NGINX reverse proxies by sending crafted HTTP requests.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2020-5416?
CVE-2020-5416 is a high-severity denial of service vulnerability in Cloud Foundry CF Deployment, published on 21 Aug 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Cloud Foundry Routing (Gorouter), versions prior to 0.204.0, when used in a deployment with NGINX reverse proxies in front of the Gorouters, is potentially vulnerable to denial-of-service attacks in which an unauthenticated malicious attacker can send specially-crafted HTTP requests that may cause the Gorouters to be dropped from the NGINX backend pool.
Weakness: CWE-404
Which versions are affected by CVE-2020-5416?
It affects 2 products.
Products include Cloudfoundry Cf-Deployment, Cloudfoundry Routing-Release.
How do I fix CVE-2020-5416?
No fix has been published for CVE-2020-5416 yet. Limit exposure of the affected software until one is available.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is CVE-2020-5416 being exploited?
There is no known exploitation of CVE-2020-5416 in the wild and no public exploit code.
Other vulnerabilities in Cloud Foundry CF Deployment
- CVE-2022-31733 Auth bypass in Cloud Foundry Diego and CF Deployment
- CVE-2020-5402 UAA fails to check the state parameter when authenticating with external IDPs
- CVE-2019-11293 UAA logs all query parameters with debug logging level
- CVE-2019-11290 Cloud Foundry UAA logs query parameters in tomcat access file
- CVE-2019-11283 Password leak in smbdriver logs