Pivotal Software Cloud Foundry UAA-release 57

CPE Details

Pivotal Software Cloud Foundry UAA-release 57
57
2018-06-26
16h23 +00:00
2018-06-26
16h23 +00:00
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
Notifications manage

CPE Name: cpe:2.3:a:pivotal_software:cloud_foundry_uaa-release:57:*:*:*:*:*:*:*

Informations

Vendor

pivotal_software

Product

cloud_foundry_uaa-release

Version

57

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2019-11268 2019-07-11 18h11 +00:00 Cloud Foundry UAA version prior to 73.3.0, contain endpoints that contains improper escaping. An authenticated malicious user with basic read privileges for one identity zone can extend those reading privileges to all other identity zones and obtain private information on users, clients, and groups in all other identity zones.
4.3
Medium
CVE-2019-3787 2019-06-19 22h28 +00:00 Cloud Foundry UAA, versions prior to 73.0.0, falls back to appending “unknown.org” to a user's email address when one is not provided and the user name does not contain an @ character. This domain is held by a private company, which leads to attack vectors including password recovery emails sent to a potentially fraudulent address. This would allow the attacker to gain complete control of the user's account.
8.8
High
CVE-2018-11041 2018-06-25 15h00 +00:00 Cloud Foundry UAA, versions later than 4.6.0 and prior to 4.19.0 except 4.10.1 and 4.7.5 and uaa-release versions later than v48 and prior to v60 except v55.1 and v52.9, does not validate redirect URL values on a form parameter used for internal UAA redirects on the login page, allowing open redirects. A remote attacker can craft a malicious link that, when clicked, will redirect users to arbitrary websites after a successful login attempt.
6.1
Medium
CVE-2018-1262 2018-05-15 20h00 +00:00 Cloud Foundry Foundation UAA, versions 4.12.X and 4.13.X, introduced a feature which could allow privilege escalation across identity zones for clients performing offline validation. A zone administrator could configure their zone to issue tokens which impersonate another zone, granting up to admin privileges in the impersonated zone for clients performing offline token validation.
7.2
High