Note:
This project will be discontinued after December 13, 2021. [more]
Product:
Cloud_foundry_uaa
(Pivotal_software)Repositories |
Unknown: This might be proprietary software. |
#Vulnerabilities | 32 |
Date | Id | Summary | Products | Score | Patch | Annotated |
---|---|---|---|---|---|---|
2017-03-10 | CVE-2017-4960 | An issue was discovered in Cloud Foundry release v247 through v252, UAA stand-alone release v3.9.0 through v3.11.0, and UAA Bosh Release v21 through v26. There is a potential to subject the UAA OAuth clients to a denial of service attack. | Cloud_foundry_uaa_bosh, Cloud_foundry, Cloud_foundry_uaa | 7.5 | ||
2017-05-25 | CVE-2016-0781 | The UAA OAuth approval pages in Cloud Foundry v208 to v231, Login-server v1.6 to v1.14, UAA v2.0.0 to v2.7.4.1, UAA v3.0.0 to v3.2.0, UAA-Release v2 to v7 and Pivotal Elastic Runtime 1.6.x versions prior to 1.6.20 are vulnerable to an XSS attack by specifying malicious java script content in either the OAuth scopes (SCIM groups) or SCIM group descriptions. | Cloud_foundry_uaa_bosh, Cloud_foundry, Cloud_foundry_elastic_runtime, Cloud_foundry_uaa, Login\-Server | 6.1 | ||
2017-05-25 | CVE-2016-3084 | The UAA reset password flow in Cloud Foundry release v236 and earlier versions, UAA release v3.3.0 and earlier versions, all versions of Login-server, UAA release v10 and earlier versions and Pivotal Elastic Runtime versions prior to 1.7.2 is vulnerable to a brute force attack due to multiple active codes at a given time. This vulnerability is applicable only when using the UAA internal user store for authentication. Deployments enabled for integration via SAML or LDAP are not affected. | Cloud_foundry_uaa_bosh, Cloud_foundry, Cloud_foundry_elastic_runtime, Cloud_foundry_uaa, Login\-Server | 8.1 | ||
2017-06-13 | CVE-2017-4994 | An issue was discovered in Cloud Foundry Foundation cf-release versions prior to v263; UAA release 2.x versions prior to v2.7.4.18, 3.6.x versions prior to v3.6.12, 3.9.x versions prior to v3.9.14, and other versions prior to v4.3.0; and UAA bosh release (uaa-release) 13.x versions prior to v13.16, 24.x versions prior to v24.11, 30.x versions prior to 30.4, and other versions prior to v40. There was an issue with forwarded http headers in UAA that could result in account corruption. | Cloud_foundry_uaa_bosh, Cloud_foundry_cf, Cloud_foundry_uaa | 7.5 | ||
2019-07-18 | CVE-2019-3794 | Cloud Foundry UAA, versions prior to v73.4.0, does not set an X-FRAME-OPTIONS header on various endpoints. A remote user can perform clickjacking attacks on UAA's frontend sites. | Cloud_foundry_uaa | 5.4 | ||
2018-11-19 | CVE-2018-15761 | Cloud Foundry UAA release, versions prior to v64.0, and UAA, versions prior to 4.23.0, contains a validation error which allows for privilege escalation. A remote authenticated user may modify the url and content of a consent page to gain a token with arbitrary scopes that escalates their privileges. | Cloud_foundry_uaa, Cloudfoundry_uaa_release | 8.8 | ||
2019-08-05 | CVE-2019-11270 | Cloud Foundry UAA versions prior to v73.4.0 contain a vulnerability where a malicious client possessing the 'clients.write' authority or scope can bypass the restrictions imposed on clients created via 'clients.write' and create clients with arbitrary scopes that the creator does not possess. | Application_service, Cloud_foundry_uaa, Operations_manager | 7.5 | ||
2017-06-13 | CVE-2017-4963 | An issue was discovered in Cloud Foundry Foundation Cloud Foundry release v252 and earlier versions, UAA stand-alone release v2.0.0 - v2.7.4.12 & v3.0.0 - v3.11.0, and UAA bosh release v26 & earlier versions. UAA is vulnerable to session fixation when configured to authenticate against external SAML or OpenID Connect based identity providers. | Cloud_foundry_cf\-Release, Cloud_foundry_uaa, Cloud_foundry_uaa\-Release | 8.1 | ||
2018-02-01 | CVE-2018-1192 | In Cloud Foundry Foundation cf-release versions prior to v285; cf-deployment versions prior to v1.7; UAA 4.5.x versions prior to 4.5.5, 4.8.x versions prior to 4.8.3, and 4.7.x versions prior to 4.7.4; and UAA-release 45.7.x versions prior to 45.7, 52.7.x versions prior to 52.7, and 53.3.x versions prior to 53.3, the SessionID is logged in audit event logs. An attacker can use the SessionID to impersonate a logged-in user. | Cloud_foundry_cf\-Deployment, Cloud_foundry_cf\-Release, Cloud_foundry_uaa, Cloud_foundry_uaa\-Release | 8.8 | ||
2018-07-24 | CVE-2018-11047 | Cloud Foundry UAA, versions 4.19 prior to 4.19.2 and 4.12 prior to 4.12.4 and 4.10 prior to 4.10.2 and 4.7 prior to 4.7.6 and 4.5 prior to 4.5.7, incorrectly authorizes requests to admin endpoints by accepting a valid refresh token in lieu of an access token. Refresh tokens by design have a longer expiration time than access tokens, allowing the possessor of a refresh token to authenticate longer than expected. This affects the administrative endpoints of the UAA. i.e. /Users, /Groups, etc.... | Cloud_foundry_uaa | 7.5 |