CVE-2019-3787
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, versions prior to 73.0.0, falls back to appending “unknown.org” to a user's email address when one is not provided and the user name does not contain an @ character. This domain is held by a private company, which leads to attack vectors including password recovery emails sent to a potentially fraudulent address. This would allow the attacker to gain complete control of the user's account.
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 versions prior to 73.0.0 contain a flawed fallback mechanism that appends 'unknown.org' domain to usernames without @ symbols when no email address is provided. Since unknown.org is controlled by a private company, password reset and recovery emails are routed to an attacker-controlled address, enabling complete account takeover.
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< 73.0.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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 UAA versionLocate your Cloud Foundry UAA release version through your deployment manifest, BOSH release information, or Pivotal Ops Manager. Compare the installed version against the affected range of versions prior to 73.0.0.Affected if Your UAA version is less than 73.0.0
-
Search for unknown.org in UAA configurationSearch UAA configuration files, YAML manifests, and environment variables for the string 'unknown.org'. Check both deployment configs and any database records that store user domain settings.Affected if The string 'unknown.org' appears in your UAA configuration or is being used as a fallback domain
-
Verify email fallback behaviorExamine UAA configuration related to email address handling for users without @ symbols. Look for logic that automatically appends a domain to usernames during user creation or password reset operations.Affected if Your UAA appends a domain to usernames that lack an @ symbol when no email is provided
-
Check password reset email routingReview the email provider and routing configuration for UAA password reset and account recovery flows. Determine where password reset emails are actually being sent for users created without explicit email addresses.Affected if Password reset emails for users without email addresses are routed to an external domain you do not control
You are affected if your UAA version is below 73.0.0 and the unknown.org domain fallback is active in your configuration, causing usernames without @ symbols to receive password reset emails at an attacker-controlled domain.
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 data73.0.0
Upgrade UAA to version 73.0.0 or later which removes the unknown.org domain fallback behavior.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3787 — 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-3787 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