Vulnerabilities > Cloudfoundry > CF Deployment > 13.20.0
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2023-09-08 | CVE-2023-34041 | Unspecified vulnerability in Cloudfoundry Routing-Release Cloud foundry routing release versions prior to 0.278.0 are vulnerable to abuse of HTTP Hop-by-Hop Headers. | 5.3 |
| 2022-03-25 | CVE-2021-22100 | Resource Exhaustion vulnerability in Cloudfoundry Capi-Release In cloud foundry CAPI versions prior to 1.122, a denial-of-service attack in which a developer can push a service broker that (accidentally or maliciously) causes CC instances to timeout and fail is possible. | 5.3 |
| 2021-10-27 | CVE-2021-22101 | Resource Exhaustion vulnerability in Cloudfoundry Capi-Release 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 label_selectors on multiple V3 endpoints by generating an enormous SQL query. | 7.5 |
| 2021-08-11 | CVE-2021-22098 | Open Redirect vulnerability in Cloudfoundry User Account and Authentication UAA server versions prior to 75.4.0 are vulnerable to an open redirect vulnerability. | 6.1 |
| 2021-07-22 | CVE-2021-22001 | Unspecified vulnerability in Cloudfoundry User Account and Authentication In UAA versions prior to 75.3.0, sensitive information like relaying secret of the provider was revealed in response when deletion request of an identity provider( IdP) of type “oauth 1.0” was sent to UAA server. | 7.5 |
| 2021-04-08 | CVE-2021-22115 | Insufficiently Protected Credentials vulnerability in Cloudfoundry Capi-Release Cloud Controller API versions prior to 1.106.0 logs service broker credentials if the default value of db logging config field is changed. | 6.5 |
| 2020-12-02 | CVE-2020-5423 | Resource Exhaustion vulnerability in Cloudfoundry Cf-Deployment 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 YAML parser to consume excessive CPU and RAM. | 7.5 |