Diego vulnerabilitiesRanked by how likely they are to be used.
Diego is made by Cloudfoundry. We track 1 published vulnerability in it, across 150 versions. None of them is on the list of flaws known to be exploited today. If you run Diego, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Diego vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Diego's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Diego 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.
- 0.4%CVE-2022-31733Critical
Starting with diego-release 2.55.0 and up to 2.69.0, and starting with CF Deployment 17.1 and up to 23.2.0, apps are accessible via another port on diego cells, allowing application ingress without a client certificate.
Running Diego? 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
Starting with diego-release 2.55.0 and up to 2.69.0, and starting with CF Deployment 17.1 and up to 23.2.0, apps are accessible via another port on diego cells, allowing application ingress without a client certificate. If mTLS route integrity is enabled AND unproxied ports are turned off, then an attacker could connect to an application that should be only reachable via mTLS, without presenting a client certificate.
- Matched to
- Diego 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 1 published vulnerability listed under the name Diego, across 150 versions.
None of Diego's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Diego. 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.