Skip to content

GHSA-xg5v-696h-c3vr CVE-2018-1192

Cloud Foundry UAA SessionID present in Audit Event Logs

High Maven
Severity
8.8 / 10
High · CVSS 3.0
Exploit chance (EPSS)
1.01%
Chance of exploitation in the next 30 days. Higher than 63.30% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Fix
4.5.5
Upgrade org.cloudfoundry.identity:cloudfoundry-identity-server to this version or later

Description

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.

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.5.5

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

Severity breakdown

CVSS 3.0 8.8

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

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

Weakness

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How to prevent it
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

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-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-j4p3-2m2h-cv5f
Cloud Foundry UAA Denial of Service through client token revocation 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