GHSA-fm5c-2rwc-887w CVE-2016-3084
Cloud Foundry UAA reset password vulnerable to brute force attack
- Severity
- 8.1 / 10
- High · CVSS 3.0
- Exploit chance (EPSS)
- 1.19%
- Chance of exploitation in the next 30 days. Higher than 67.96% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- —
- Not classified
- Fix
3.3.0.1- Upgrade org.cloudfoundry.identity:cloudfoundry-identity-server to this version or later
Description
The UAA reset password flow in Cloud Foundry release v236 and earlier versions, UAA release v3.3.0 and earlier versions, all versions of Login-server, UAA release v10 and earlier versions and Pivotal Elastic Runtime versions prior to 1.7.2 is vulnerable to a brute force attack due to multiple active codes at a given time. This vulnerability is applicable only when using the UAA internal user store for authentication. Deployments enabled for integration via SAML or LDAP are not affected.
Affected versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| org.cloudfoundry.identity:cloudfoundry-identity-server | < 3.3.0.1 |
3.3.0.1 |
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 → 3.3.0.1
- maven
<dependency><groupId>org.cloudfoundry.identity</groupId><artifactId>cloudfoundry-identity-server</artifactId><version>3.3.0.1</version></dependency>- gradle
implementation("org.cloudfoundry.identity:cloudfoundry-identity-server:3.3.0.1")
Severity breakdown
CVSS 3.0 8.1
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
References
Advisories
Packages
Other links
- github.com/cloudfoundry/uaa/commit/14350228989e2aee900b8d48a848293bb5152b6f
- github.com/cloudfoundry/uaa/commit/1d3ad7399d010f6a29dc3bf8139d792121301ab8
- github.com/cloudfoundry/uaa/commit/460627ed419e4227b10ff121248b3ffc009011a9
- github.com/cloudfoundry/uaa/commit/4a119d314744460ed56bcd740b2e913bf3f560c1
- github.com/cloudfoundry/uaa/commit/5c2377487bef9d716d5c8e5717df1fc00bc7b000
- github.com/cloudfoundry/uaa/commit/66132926f1bac0b878da5841be2f93fa5075d88f
- github.com/cloudfoundry/uaa/commit/b3834364ab573e9655348193780a56a602fe87b7
- pivotal.io/security/cve-2016-3084
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why 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 |
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