This page lists publicly disclosed CVE vulnerabilities affecting cloudfoundry uaa_release (linked via NVD CPE). Each row includes severity scores, summaries, and publication dates to help identify and analyze security issues.
| CVE | Summary | Source | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|---|
| CVE-2025-22246 | Cloud Foundry UAA release versions from v77.21.0 to v7.31.0 are vulnerable to a private key exposure in logs. | [email protected] | 3.0 | 0.18% | 2025-05-13 | 2025-07-11 |
| CVE-2019-11279 | CF UAA versions prior to 74.1.0 can request scopes for a client that shouldn't be allowed by submitting an array of requested scopes. A remote malicious user can escalate their own privileges to any scope, allowing them to take control of UAA and the resources it controls. | [email protected] | 8.8 | 0.39% | 2019-09-26 | 2024-11-21 |
| CVE-2019-3801 | Cloud Foundry cf-deployment, versions prior to 7.9.0, contain java components that are using an insecure protocol to fetch dependencies when building. A remote unauthenticated malicious attacker could hijack the DNS entry for the dependency, and inject malicious code into the component. | [email protected] | 9.8 | 0.07% | 2019-04-25 | 2024-11-21 |
| CVE-2019-3788 | Cloud Foundry UAA Release, versions prior to 71.0, allows clients to be configured with an insecure redirect uri. Given a UAA client was configured with a wildcard in the redirect uri's subdomain, a remote malicious unauthenticated user can craft a phishing link to get a UAA access code from the victim. | [email protected] | 8.7 | 0.50% | 2019-04-25 | 2024-11-21 |
| CVE-2019-3775 | Cloud Foundry UAA, versions prior to v70.0, allows a user to update their own email address. A remote authenticated user can impersonate a different user by changing their email address to that of a different user. | [email protected] | 7.1 | 0.09% | 2019-03-07 | 2024-11-21 |