Skip to content
Fencer Intel
critical 9.8

CVE-2015-5171 json

Cloud Foundry Runtime Insufficient Session Expiration vulnerability

published 9y ago modified 4mo ago also GHSA-h533-q6jc-qx28 , EUVD-2022-4065

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 67%
public exploits
0
none known

Summary

The password change functionality in 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 existing sessions.

Patch / fix

  • maven org.cloudfoundry.identity:cloudfoundry-identity-server 2.5.2
  • cloudfoundry cf-release 216
  • pivotal_software cloud_foundry_elastic_runtime 1.7.0
  • pivotal_software cloud_foundry_uaa 2.5.2

Is CVE-2015-5171 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.17% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.cloudfoundry.identity:cloudfoundry-identity-server
<2.5.2
2.5.2

Classification

Weakness
  • CWE-613 DEPRECATED: Insufficient Session Expiration

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.