Capi-Release vulnerabilitiesRanked by how likely they are to be used.
Capi-Release is made by Cloudfoundry. We track 22 published vulnerabilities in it, across 221 versions. None of them is on the list of flaws known to be exploited today. If you run Capi-Release, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Capi-Release vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Capi-Release's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Capi-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.
- 1.7%CVE-2016-9882High
An issue was discovered in Cloud Foundry Foundation cf-release versions prior to v250 and CAPI-release versions prior to v1.12.0.
- 1.4%CVE-2017-8036High
An issue was discovered in the Cloud Controller API in Cloud Foundry Foundation CAPI-release version 1.33.0 (only).
- 1.3%CVE-2019-3798High
Cloud Foundry Cloud Controller API Release, versions prior to 1.79.0, contains improper authentication when validating user permissions.
- 1.3%CVE-2019-3785High
Cloud Foundry Cloud Controller, versions prior to 1.78.0, contain an endpoint with improper authorization.
- 1.1%CVE-2020-5423High
CAPI (Cloud Controller) versions prior to 1.101.0 are vulnerable to a denial-of-service attack in which an unauthenticated malicious attacker can send specially-crafted YAML files to certain endpoints, causing the...
- 1.1%CVE-2018-1266High
Cloud Foundry Cloud Controller, versions prior to 1.52.0, contains information disclosure and path traversal vulnerabilities.
- 1.0%CVE-2017-8033High
An issue was discovered in the Cloud Controller API in Cloud Foundry Foundation CAPI-release versions prior to v1.35.0 and cf-release versions prior to v268.
- 1.0%CVE-2021-22101High
Cloud Controller versions prior to 1.118.0 are vulnerable to unauthenticated denial of Service(DoS) vulnerability allowing unauthenticated attackers to cause denial of service by using REST HTTP requests with...
Running Capi-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
An issue was discovered in Cloud Foundry Foundation cf-release versions prior to v250 and CAPI-release versions prior to v1.12.0. Cloud Foundry logs the credentials returned from service brokers in Cloud Controller system component logs. These logs are written to disk and often sent to a log aggregator via syslog.
- Matched to
- Capi-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 22 published vulnerabilities listed under the name Capi-Release, across 221 versions.
None of Capi-Release's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Capi-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.