CVE-2016-3084
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 · uneditedThe UAA reset password flow in Cloud Foundry release v236 and earlier versions, UAA release v3.3.0 and earlier versions, all versions of Login-server, UAA release v10 and earlier versions and Pivotal Elastic Runtime versions prior to 1.7.2 is vulnerable to a brute force attack due to multiple active codes at a given time. This vulnerability is applicable only when using the UAA internal user store for authentication. Deployments enabled for integration via SAML or LDAP are not affected.
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 confidenceThe UAA (User Account and Authentication) password reset flow in affected Cloud Foundry versions allows multiple active password reset codes to exist simultaneously. This design flaw enables attackers to conduct brute force attacks by systematically guessing valid reset codes, since rate limiting is ineffective when multiple codes can be active at once. The vulnerability only affects deployments using the UAA internal user store; SAML or LDAP integrated configurations are not vulnerable.
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<= 10<= 236<= 1.7.1<= 3.3.0all versionsCVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/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.
-
Identify authentication configurationExamine UAA configuration files (uaa.yml or login.yml) to determine if internal user store is in use, or if SAML/LDAP integration is configured. Look for 'uaa' or 'internal' as the identity provider, versus 'saml' or 'ldap' provider settings.Affected if Using the UAA internal user store (uaa) as the identity provider; SAML or LDAP configurations are not affected
-
Check UAA versionRun 'uaac version' or check the UAA Bosh release version via 'bosh releases' command. Compare against affected versions: Cloud Foundry Uaa Bosh <= 10, Pivotal Cloud Foundry Uaa <= 3.3.0Affected if UAA Bosh release version is 10 or lower, or Pivotal Cloud Foundry Uaa version is 3.3.0 or lower
-
Check Cloud Foundry versionRun 'cf version' or check via BOSH deployment manifest. Compare against affected version: Pivotal Cloud Foundry <= 236Affected if Cloud Foundry version is 236 or lower
-
Check Elastic Runtime versionCheck the Pivotal Elastic Runtime version via BOSH or Ops Manager. Compare against affected version: Pivotal Cloud Foundry Elastic Runtime <= 1.7.1Affected if Elastic Runtime version is 1.7.1 or lower
-
Check Login Server versionCheck the Login Server version via BOSH releases if deployed. Note that all versions of Login Server are affected per the advisory.Affected if Login Server is deployed (all versions are affected)
You are affected if using the UAA internal user store and any of these conditions are true: UAA Bosh <= 10, Cloud Foundry <= 236, Elastic Runtime <= 1.7.1, Uaa <= 3.3.0, or Login Server is deployed. SAML or LDAP integrated deployments are not affected.
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 dataUpgrade UAA to version v3.4.0+, v11+, or Pivotal Elastic Runtime 1.7.2+ to receive the fix that limits active password reset codes to one per user at a time. Deployments using SAML or LDAP integration are not affected and require no action.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-3084 — 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-2016-3084 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