UAA redirect-uri allows wildcard in the subdomain

published 2019-04-25 7y ago modified 2026-06-17 4mo ago also EUVD-2019-13419

cvss: 8.7; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.8%; EPSS 0.8% chance of exploitation in 30 days, percentile 57%
public exploits: 0; none known

Cloud Foundry UAA Release, versions prior to 71.0, allows clients to be configured with an insecure redirect uri. Given a UAA client was configured with a wildcard in the redirect uri's subdomain, a remote malicious unauthenticated user can craft a phishing link to get a UAA access code from the victim.

Patch / fix

fixed in 2

Cloud Foundry UAA Release (OSS) v71.0
Pivotal Pivotal Application Service 2.5.1

Is CVE-2019-3788 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

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

CVSS scores

assigned by	version	score	vector
CNA	3.0	8.7	CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
NVD	3.0	6.1	CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD	2.0	5.8	AV:N/AC:M/Au:N/C:P/I:P/A:N

Affected products

Cloud Foundry UAA Release (OSS)
Pivotal Pivotal Application Service

Classification

Weakness

CWE-601 URL Redirection to Untrusted Site

References

cloudfoundry.org /blog/cve-2019-3788
vendor-advisory

Sources

CVE List CVE-2019-3788
NVD CVE-2019-3788

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.