Skip to content

GHSA-j4p3-2m2h-cv5f CVE-2017-8031

Cloud Foundry UAA Denial of Service through client token revocation endpoint

Medium Maven
Severity
5.3 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
1.09%
Chance of exploitation in the next 30 days. Higher than 65.27% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
—
Not classified
Fix
4.7.1
Upgrade org.cloudfoundry.identity:cloudfoundry-identity-server to this version or later

Description

An issue was discovered in Cloud Foundry Foundation cf-release (all versions prior to v279) and UAA (30.x versions prior to 30.6, 45.x versions prior to 45.4, 52.x versions prior to 52.1). In some cases, the UAA allows an authenticated user for a particular client to revoke client tokens for other users on the same client. This occurs only if the client is using opaque tokens or JWT tokens validated using the check_token endpoint. A malicious actor could cause denial of service.

Affected versions

Maven

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.cloudfoundry.identity:cloudfoundry-identity-server Maven → 4.7.1

maven
<dependency><groupId>org.cloudfoundry.identity</groupId><artifactId>cloudfoundry-identity-server</artifactId><version>4.7.1</version></dependency>
gradle
implementation("org.cloudfoundry.identity:cloudfoundry-identity-server:4.7.1")

Severity breakdown

CVSS 3.1 5.3

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-6wcw-r64p-qrrw
Cloudfoundry UAA has logic error in the token revocation endpoint implementation
Medium Also affects org.cloudfoundry.identity:cloudfoundry-identity-server
GHSA-xg5v-696h-c3vr
Cloud Foundry UAA SessionID present in Audit Event Logs
High Also affects org.cloudfoundry.identity:cloudfoundry-identity-server
GHSA-xh4m-99qp-w483
Cloud Foundry UAA open redirect
Medium Also affects org.cloudfoundry.identity:cloudfoundry-identity-server
GHSA-rc2r-w8jv-vggp
Cloud Foundry vulnerable to Improper Certificate Validation
Medium Also affects org.cloudfoundry.identity:cloudfoundry-identity-server
GHSA-r4v8-9hgx-vm6m
Cloud Foundry UAA accepts refresh token as access token on admin endpoints
High Also affects org.cloudfoundry.identity:cloudfoundry-identity-server
GHSA-292x-hjr8-226f
Cloud Foundry UAA Privilege Escalation
High Also affects org.cloudfoundry.identity:cloudfoundry-identity-server
GHSA-j97q-9xp9-g5fx
Pivotal Cloud Foundry UAA XSS on UAA OpenID Connect check session iframe endpoint
Medium Also affects org.cloudfoundry.identity:cloudfoundry-identity-server
GHSA-9frw-wmvq-5rrc
Cloud Foundry UAA Identity Zone Admin Privilege Escalation
Medium Also affects org.cloudfoundry.identity:cloudfoundry-identity-server
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor