CVE-2018-1262
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 Foundation UAA, versions 4.12.X and 4.13.X, introduced a feature which could allow privilege escalation across identity zones for clients performing offline validation. A zone administrator could configure their zone to issue tokens which impersonate another zone, granting up to admin privileges in the impersonated zone for clients performing offline token validation.
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) server in Cloud Foundry versions 4.12.X and 4.13.X contains a privilege escalation vulnerability where zone administrators can configure their zone to issue tokens that impersonate another zone. When clients perform offline token validation against these maliciously configured tokens, they receive up to admin privileges in the impersonated zone.
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.12.0= 4.12.1= 4.12.2= 4.13.0= 4.13.1= 4.13.2= 4.13.3= 4.13.4= 57= 57.1= 58>= 1.27.0, <= 1.31.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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/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 UAA versionCheck the UAA version by querying the UAA endpoint /info or reviewing the deployment manifest/versions file for the UAA releaseAffected if The installed version is 4.12.0, 4.12.1, 4.12.2, 4.13.0, 4.13.1, 4.13.2, 4.13.3, or 4.13.4
-
Identify UAA Release versionReview the Cloud Foundry deployment manifest or release notes to determine the UAA Release version numberAffected if UAA Release is version 57, 57.1, or 58
-
Identify CF Deployment versionCheck the cf-deployment version by running 'cf version' or reviewing the deployment manifest fileAffected if CF Deployment version is between 1.27.0 and 1.31.0 inclusive
-
Review zone administrator configurationsInspect the UAA zone configuration files and database for any zone administrators with cross-zone impersonation settings. Look for zone-related XML or YAML configuration files in the UAA deployment directoryAffected if Any zone administrator has configured their zone to issue tokens that impersonate a different zone, granting elevated privileges in the target zone
You are affected if your UAA version is 4.12.0-4.13.4, UAA Release 57-58, or CF Deployment 1.27.0-1.31.0 AND any zone administrator has configured cross-zone impersonation in your environment.
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 4.14.0 or later which contains the fix for this vulnerability, and review zone administrator configurations to detect any instances of cross-zone impersonation.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1262 — 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-1262 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