CVE-2018-11086
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 · uneditedPivotal Usage Service in Pivotal Application Service, versions 2.0 prior to 2.0.21 and 2.1 prior to 2.1.13 and 2.2 prior to 2.2.5, contains a bug which may allow escalation of privileges. A space developer with access to the system org may be able to access an artifact which contains the CF admin credential, allowing them to escalate to an admin role.
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 confidencePivotal Usage Service in Pivotal Application Service contains a path traversal or access control bug that allows a space developer with system org access to retrieve an artifact containing the CF admin credentials. This unauthorized credential disclosure enables privilege escalation to admin role.
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>= 2.0.0, < 2.0.21>= 2.1.0, < 2.1.13>= 2.2.0, < 2.2.5CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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.
-
Check Pivotal Application Service versionQuery the Ops Manager or use the cf CLI command 'cf version' or check the installation manifest to identify the installed PAS versionAffected if The installed version falls within 2.0.0 to 2.0.20, 2.1.0 to 2.1.12, or 2.2.0 to 2.2.4 (prior to the patched releases)
-
Verify Pivotal Usage Service is enabledCheck the PAS tile configuration in Ops Manager or review the deployment manifest for the 'p-usage-service' or 'usage-service' componentAffected if Pivotal Usage Service is deployed and enabled in the environment
-
Identify users with space developer role in system orgUse 'cf org-users system' and 'cf space-users system <space_name>' to enumerate users and their roles in the system organizationAffected if There exist users with the Space Developer role in the system organization (this is the attacker condition required for exploitation)
-
Check for anomalous credential retrieval patternsReview Usage Service logs for path traversal requests or unauthorized access attempts to admin credential artifactsAffected if Logs show requests for paths like '../credentials' or similar path traversal patterns targeting admin credentials
You are affected if you run a vulnerable PAS version (2.0.x before 2.0.21, 2.1.x before 2.1.13, or 2.2.x before 2.2.5) with Pivotal Usage Service enabled and users exist who have space developer access to the system organization.
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 data2.0.212.1.132.2.5
Upgrade Pivotal Usage Service to version 2.0.21, 2.1.13, or 2.2.5 or later per the Pivotal security advisory. Additionally, rotate any compromised admin credentials as a precautionary measure.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-11086 — 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-11086 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