Skip to content

GHSA-cq6m-74r4-x77g CVE-2015-5172

Cloud Foundry Runtime has Weak Password Recovery Mechanism for Forgotten Password

Critical Maven
Severity
9.8 / 10
Critical · CVSS 3.1
Exploit chance (EPSS)
1.17%
Chance of exploitation in the next 30 days. Higher than 67.34% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-640 Weak Password Recovery Mechanism for Forgotten Password
Fix
2.5.2
Upgrade org.cloudfoundry.identity:cloudfoundry-identity-server to this version or later

Description

Cloud Foundry Runtime cf-release before 216, UAA before 2.5.2, and Pivotal Cloud Foundry (PCF) Elastic Runtime before 1.7.0 allow attackers to have unspecified impact by leveraging failure to expire password reset links.

Affected versions

Maven

PackageVulnerableFixed in
org.cloudfoundry.identity:cloudfoundry-identity-server
< 2.5.2
2.5.2

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 → 2.5.2

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

Severity breakdown

CVSS 3.1 9.8

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

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

Weakness

CWE-640: Weak Password Recovery Mechanism for Forgotten Password

The product contains a mechanism for users to recover or change their passwords without knowing the original password, but the mechanism is weak.

How to prevent it
  • Architecture and Design: Make sure that all input supplied by the user to the password recovery mechanism is thoroughly filtered and validated.
  • Architecture and Design: Do not use standard weak security questions and use several security questions.
  • Architecture and Design: Make sure that there is throttling on the number of incorrect answers to a security question. Disable the password recovery functionality after a certain (small) number of incorrect guesses.
  • Architecture and Design: Require that the user properly answers the security question prior to resetting their password and sending the new password to the e-mail address of record.
  • Architecture and Design: Never allow the user to control what e-mail address the new password will be sent to in the password recovery mechanism.
  • Architecture and Design: Assign a new temporary password rather than revealing the original password.

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