CVE-2017-4994
HighSummary
An issue was discovered in Cloud Foundry Foundation cf-release versions prior to v263 and in UAA across various versions, concerning forwarded HTTP headers. This could lead to account corruption.
Risk Assessment
Organizations may be at risk of losing the integrity of user accounts, potentially leading to unauthorized access or data loss.
Recommendation
It is recommended to upgrade to the latest versions of cf-release and UAA to mitigate the risk associated with this vulnerability.
Other vulnerabilities in Cloud Foundry Foundation cf-release, UAA
See all- CVE-2017-4991High
An issue was discovered in Cloud Foundry Foundation cf-release versions prior to v260 and in UAA versions prior to specified versions, allowing privileged users in one zone to reset passwords for users in a different zone.
- CVE-2017-4973High
A vulnerability was discovered in Cloud Foundry Foundation cf-release versions prior to v257 and in UAA versions 2.x prior to v2.7.4.14, 3.6.x prior to v3.6.8, 3.9.x prior to v3.9.10, and others prior to v3.15.0. The vulnerability affects the groups endpoint in UAA, allowing users to elevate their privileges.
- CVE-2017-4972High
An issue was discovered in Cloud Foundry Foundation cf-release versions prior to v257 and in UAA versions prior to specified versions, allowing an attacker to perform a blind SQL injection attack on the UAA database.
- CVE-2017-4992Critical
An issue was discovered in Cloud Foundry Foundation cf-release versions prior to v261 and UAA versions prior to specified versions, allowing privilege escalation through arbitrary password resets with user invitations.
Original NVD description (English source)
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.