Skip to content
Fencer Intel
high 7.3

CVE-2019-11270 json

UAA clients.write vulnerability

published 7y ago modified 4mo ago also EUVD-2019-2959

cvss
7.3
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 66%
public exploits
0
none known

Summary

Cloud Foundry UAA versions prior to v73.4.0 contain a vulnerability where a malicious client possessing the 'clients.write' authority or scope can bypass the restrictions imposed on clients created via 'clients.write' and create clients with arbitrary scopes that the creator does not possess.

Patch / fix

  • pivotal_software application_service 2.3.15, 2.4.11, 2.5.7, 2.6.2
  • pivotal_software cloud_foundry_uaa 73.4.0
  • pivotal_software operations_manager 2.3.22, 2.4.16, 2.5.10, 2.6.4

Is CVE-2019-11270 in your stack? 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.12% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.0 7.3 CVSS:3.0/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:N
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N

Affected products

  • Cloud Foundry UAA Release (OSS)

Classification

Weakness
  • CWE-269 Improper Privilege Management
  • CWE-732 Incorrect Permission Assignment for Critical Resource

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.