Security readout for executives and security teams
Plain-English summary
Cloud Foundry UAA accepted refresh tokens where admin access tokens were expected. Because refresh tokens usually last longer, someone holding a valid refresh token could remain able to reach administrative UAA functions longer than intended.
Executive priority
Treat this as a priority upgrade for any affected Cloud Foundry UAA deployment because it concerns administrative endpoints and longer-lived tokens. Urgency is lower if fixed versions are already deployed or admin endpoints are tightly restricted.
Technical view
CVE-2018-11047 affects Cloud Foundry UAA 4.19 before 4.19.2, 4.12 before 4.12.4, 4.10 before 4.10.2, 4.7 before 4.7.6, and 4.5 before 4.5.7. Admin endpoints such as /Users and /Groups incorrectly authorized valid refresh tokens.
Likely exposure
Exposure is limited to deployments running the listed vulnerable Cloud Foundry UAA release branches. Risk is most relevant where UAA administrative endpoints are reachable and refresh tokens could be obtained or retained by users, clients, or systems.
Exploitation context
The supplied sources do not show CISA KEV listing or active exploitation. The vulnerability requires possession of a valid refresh token; tokens stop working if the user, groups, or client are removed as described by the CVE source.
Researcher notes
The source bundle does not provide CVSS, CWE, proof of concept, or exploit telemetry. Analysis should focus on version validation, administrative endpoint exposure, token lifetime assumptions, and whether refresh tokens could persist after access should have ended.
Mitigation direction
- Upgrade affected UAA branches to the fixed versions named in the advisory.
- Review Cloud Foundry vendor guidance for any environment-specific remediation steps.
- Remove stale users, groups, or clients that should no longer retain access.
- Reduce exposure of UAA administrative endpoints to trusted administrative networks only.
Validation and detection
- Inventory Cloud Foundry UAA versions across all foundations and environments.
- Confirm affected branches are at or above the fixed advisory versions.
- Review token lifecycle controls for users, groups, and clients.
- Check whether UAA administrative endpoints are reachable beyond trusted administrative paths.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Credential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2018-11047 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://www.cloudfoundry.org/blog/cve-2018-11047/CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.