Routing-Release vulnerabilitiesRanked by how likely they are to be used.
Routing-Release is made by Cloudfoundry. We track 8 published vulnerabilities in it, across 75 versions. None of them is on the list of flaws known to be exploited today. If you run Routing-Release, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Routing-Release vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Routing-Release's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Routing-Release 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.5%CVE-2019-11289High
Cloud Foundry Routing, all versions before 0.193.0, does not properly validate nonce input.
- 1.3%CVE-2016-8218Critical
An issue was discovered in Cloud Foundry Foundation routing-release versions prior to 0.142.0 and cf-release versions 203 to 231.
- 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.
- 1.1%CVE-2018-1193Medium
Cloud Foundry routing-release, versions prior to 0.175.0, lacks sanitization for user-provided X-Forwarded-Proto headers.
- 0.8%CVE-2017-8034Medium
The Cloud Controller and Router in Cloud Foundry (CAPI-release capi versions prior to v1.32.0, Routing-release versions prior to v0.159.0, CF-release versions prior to v267) do not validate the issuer on JSON Web...
- 0.4%CVE-2023-34041Medium
Cloud foundry routing release versions prior to 0.278.0 are vulnerable to abuse of HTTP Hop-by-Hop Headers.
Running Routing-Release? 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
- Routing-Release 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 8 published vulnerabilities listed under the name Routing-Release, across 75 versions.
None of Routing-Release's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Routing-Release. 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.