CVE-2018-15795
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 CredHub Service Broker, versions prior to 1.1.0, uses a guessable form of random number generation in creating service broker's UAA client. A remote malicious user may guess the client secret and obtain or modify credentials for users of the CredHub Service.
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 CredHub Service Broker versions prior to 1.1.0 use a weak, guessable form of random number generation when creating the UAA client secret. An attacker can brute-force or guess this secret to authenticate as the service broker and obtain or modify stored credentials for all users of the CredHub Service.
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< 1.1.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
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.
-
Determine CredHub Service Broker deployment methodIdentify whether the CredHub Service Broker was deployed via Pivotal Ops Manager tile, BOSH release, or cf CLI service broker command. Check your Ops Manager dashboard, BOSH deployments, or run 'cf service-brokers' to list deployed service brokers.Affected if The service broker is deployed and its version is less than 1.1.0
-
Check CredHub Service Broker version via Ops ManagerIf deployed as a Pivotal tile, open Ops Manager, locate the CredHub Service Broker tile in the Installation Dashboard, and review the installed version number shown in the tile metadata or release notes.Affected if The displayed version is prior to 1.1.0
-
Check CredHub Service Broker version via BOSHIf deployed as a BOSH release, run 'bosh -d <deployment-name> deployments' or 'bosh releases' to identify the release name and version. Look for a release named 'credhub-service-broker' or similar.Affected if The BOSH release version is less than 1.1.0
-
Check CredHub Service Broker version via cf CLIRun 'cf service-brokers' to list service brokers, then query the specific broker details with 'cf service-access' or inspect the broker URL directly. The version may be exposed in the broker metadata or response headers.Affected if The broker version reported is prior to 1.1.0
You are affected if the deployed version of Pivotal CredHub Service Broker is below 1.1.0, as only versions prior to 1.1.0 use weak random number generation for the UAA client secret.
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 data1.1.0
Upgrade Pivotal CredHub Service Broker to version 1.1.0 or later, which implements cryptographically secure random number generation for client secret creation.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15795 — 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-15795 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