Skip to content
Fencer Intel
high 8.8

CVE-2018-1192 json

Cloud Foundry UAA SessionID present in Audit Event Logs

published 2018-02-01 8 y ago modified 2026-06-17 4 mo ago also GHSA-xg5v-696h-c3vr , EUVD-2022-5778

cvss
8.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 63%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.cloudfoundry.identity:cloudfoundry-identity-server 4.5.5, 4.7.4, 4.8.3
  • pivotal_software cloud_foundry_uaa 4.5.5, 4.7.4, 4.8.3
  • pivotal_software cloud_foundry_cf-release 285
  • pivotal_software cloud_foundry_cf-deployment 1.7

Exploit prediction

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
maven org.cloudfoundry.identity:cloudfoundry-identity-server
<4.5.5
>=4.6.0, <4.7.4
>=4.8.0, <4.8.3
4.5.5
4.7.4
4.8.3

Affected products

  • n/a 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

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

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.