Skip to content

GHSA-rc2r-w8jv-vggp CVE-2016-5016

Cloud Foundry vulnerable to Improper Certificate Validation

Medium Maven
Severity
5.9 / 10
Medium · CVSS 3.0
Exploit chance (EPSS)
1.03%
Chance of exploitation in the next 30 days. Higher than 63.77% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-295 Improper Certificate Validation
Fix
3.3.0.3
Upgrade org.cloudfoundry.identity:cloudfoundry-identity-server to this version or later

Description

Pivotal Cloud Foundry 239 and earlier, UAA (aka User Account and Authentication Server) 3.4.1 and earlier, UAA release 12.2 and earlier, PCF (aka Pivotal Cloud Foundry) Elastic Runtime 1.6.x before 1.6.35, and PCF Elastic Runtime 1.7.x before 1.7.13 does not validate if a certificate is expired.

Affected versions

Maven

PackageVulnerableFixed in
org.cloudfoundry.identity:cloudfoundry-identity-server
>= 3.0.0, < 3.3.0.3
3.3.0.3
org.cloudfoundry.identity:cloudfoundry-identity-server
>= 3.4.0, < 3.4.2
3.4.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 → 3.3.0.3

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

Severity breakdown

CVSS 3.0 5.9

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

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

Weakness

CWE-295: Improper Certificate Validation

The product does not validate, or incorrectly validates, a certificate.

How to prevent it
  • Architecture and Design, Implementation: Certificates should be carefully managed and checked to assure that data are encrypted with the intended owner's public key.
  • Implementation: If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the hostname.

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