Cf-Deployment vulnerabilitiesRanked by how likely they are to be used.
Cf-Deployment is made by Cloudfoundry. We track 34 published vulnerabilities in it, across 261 versions. None of them is on the list of flaws known to be exploited today. If you run Cf-Deployment, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Cf-Deployment vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Cf-Deployment's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Cf-Deployment flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 2.9%CVE-2020-15586Medium
Go before 1.13.13 and 1.14.x before 1.14.5 has a data race in some net/http servers, as demonstrated by the httputil.ReverseProxy Handler, because it reads a request body and writes a response at the same time.
- 1.7%CVE-2018-1265High
Cloud Foundry Diego, release versions prior to 2.8.0, does not properly sanitize file paths in tar and zip files headers.
- 1.7%CVE-2019-11277High
Cloud Foundry NFS Volume Service, 1.7.x versions prior to 1.7.11 and 2.x versions prior to 2.3.0, is vulnerable to LDAP injection.
- 1.5%CVE-2019-11289High
Cloud Foundry Routing, all versions before 0.193.0, does not properly validate nonce input.
- 1.5%CVE-2019-11283High
Cloud Foundry SMB Volume, versions prior to v2.0.3, accidentally outputs sensitive information to the logs.
- 1.3%CVE-2018-1262High
Cloud Foundry Foundation UAA, versions 4.12.X and 4.13.X, introduced a feature which could allow privilege escalation across identity zones for clients performing offline validation.
- 1.3%CVE-2019-11293Medium
Cloud Foundry UAA Release, versions prior to v74.10.0, when set to logging level DEBUG, logs client_secret credentials when sent as a query parameter.
- 1.3%CVE-2019-11290High
Cloud Foundry UAA Release, versions prior to v74.8.0, logs all query parameters to tomcat’s access file.
- 1.2%CVE-2020-5416Medium
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...
- 1.2%CVE-2018-1221High
In cf-deployment before 1.14.0 and routing-release before 0.172.0, the Cloud Foundry Gorouter mishandles WebSocket requests for AWS Application Load Balancers (ALBs) and some other HTTP-aware Load Balancers.
Running Cf-Deployment? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Go before 1.13.13 and 1.14.x before 1.14.5 has a data race in some net/http servers, as demonstrated by the httputil.ReverseProxy Handler, because it reads a request body and writes a response at the same time.
- Matched to
- Cf-Deployment on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 34 published vulnerabilities listed under the name Cf-Deployment, across 261 versions.
None of Cf-Deployment's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Cf-Deployment. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.