CVE-2019-3788
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCloud 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCloud Foundry UAA Release versions prior to 71.0 contains an open redirect vulnerability where clients configured with wildcard subdomains in redirect URIs allow remote unauthenticated attackers to craft phishing links. These malicious links can steal UAA access codes from victims by abusing the overly permissive wildcard redirect URI configuration.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 71.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check the installed UAA Release versionRetrieve the UAA Release version using the BOSH CLI (bosh deployments) or check the release manifest. Compare the version number to 71.0.Affected if The UAA Release version is below 71.0.
-
List all OAuth client configurations in UAAUse the UAA CLI (uaac) with administrator credentials to run: uaac clients list. This displays all registered OAuth clients and their redirect URI configurations.Affected if Any client exists with a redirect_uri containing a wildcard pattern.
-
Identify wildcard subdomain redirect URIsExamine the redirect_uri field from the client list. Look for patterns such as '*.domain.com', 'https://*.example.com/*', or similar wildcard configurations that allow any subdomain.Affected if A client has a redirect_uri value with wildcard subdomain notation (e.g., '*.example.com').
-
Verify if the wildcard permits external malicious domainsReview the wildcard pattern scope. A vulnerable configuration would be something like '*.com' or a base domain like 'example.com' that permits subdomains the attacker controls (e.g., attacker.example.com).Affected if The wildcard redirect URI pattern is broad enough to include domains controlled by an attacker.
You are affected if your UAA Release version is below 71.0 AND you have OAuth clients configured with wildcard subdomain redirect URIs that could be exploited for phishing attacks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data71.0
Upgrade UAA Release to version 71.0 or later, and audit all client configurations to remove or restrict wildcard subdomains in redirect URIs to specific allowed domains.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3788 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-3788 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data