CVE-2018-11082
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, all versions prior to 4.20.0 and Cloud Foundry UAA Release, all versions prior to 61.0, allows brute forcing of MFA codes. A remote unauthenticated malicious user in possession of a valid username and password can brute force MFA to login as the targeted user.
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 prior to versions 4.20.0/61.0 fails to enforce rate limiting or account lockout on MFA verification, allowing an attacker with valid credentials to brute force the MFA code through repeated attempts.
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< 4.20.0< 61.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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/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 the installed UAA versionRun 'uaac target' and then 'uaac version' or check the deployed UAA release version via BOSH (bosh deployments and bosh vms). For package-based installs, check the version in the release notes or package metadata.Affected if The installed version is below 4.20.0 for UAA or below 61.0 for UAA Release.
-
Verify if MFA is enabled for user accountsCheck the UAA configuration file (uaa.yml) for 'mfa.enabled: true' or query the UAA API endpoint /oauth/clients with appropriate admin credentials to list configured identity providers with MFA settings.Affected if MFA is enabled and configured for user authentication in the UAA.
-
Confirm that rate limiting is not enforced on MFA verification attemptsReview the UAA configuration (uaa.yml) for rate limiting settings related to MFA - look for 'mfa.rateLimiter' or 'login.rateLimiter' configurations. Also check if any external rate limiting (e.g., at load balancer or firewall) is configured for the /oauth/token endpoint used for MFA verification.Affected if No rate limiting or account lockout policy is configured specifically for MFA verification attempts.
You are affected if your UAA version is below 4.20.0 (or UAA Release below 61.0), MFA is enabled, and there is no rate limiting or account lockout enforced on MFA verification attempts.
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.
dbcve · scoped4.20.061.0
Upgrade UAA to version 4.20.0 or UAA Release 61.0 or later, which implements proper rate limiting for MFA verification attempts.
UAA 4.20.0 or UAA Release 61.0
- Upgrade Cloud Foundry UAA to version 4.20.0 or later
- If using Cloud Foundry UAA Release, upgrade to version 61.0 or later
- Verify the upgrade by testing MFA authentication with incorrect attempts to confirm rate limiting is enforced
- Confirm the fix by reviewing UAA release notes for version 4.20.0 (or UAA Release 61.0) to ensure brute force protection is implemented
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-11082 — 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-2018-11082 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