dbcve.org
Broker ApiApplication · Pivotal Software

CVE-2018-15759

CRITICAL · 9.8 CVSS v3.0 Published 2018-11-19
Fix available
A fix is available. Upgrade to 0.24.0 / 3.0.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Pivotal Cloud Foundry On Demand Services SDK, versions prior to 0.24 contain an insecure method of verifying credentials. A remote unauthenticated malicious user may make many requests to the service broker with different credentials, allowing them to infer valid credentials and gain access to perform broker operations.

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 confidence

The Pivotal Cloud Foundry On Demand Services SDK versions prior to 0.24 contains an insecure credential verification mechanism that allows remote unauthenticated attackers to perform brute-force or inference attacks by sending multiple authentication requests with different credentials until valid ones are inferred, granting unauthorized access to broker operations.

MitigationUpgrade the On Demand Services SDK to version 0.24 or later which contains the fixed credential verification method.

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
Broker ApiApplication
Affected:< 3.0.2
On Demand Services SdkApplication
Affected:< 0.24.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Broker API version
    Locate the Broker API dependency or library in your project (check build.gradle, pom.xml, or vendor directory) and note the installed version number
    Affected if version is less than 3.0.2
  2. Identify On Demand Services SDK version
    Locate the On Demand Services SDK dependency in your broker project (check build files, lib directory, or vendored packages) and note the version
    Affected if version is less than 0.24.0
  3. Determine broker network exposure
    Check your broker deployment configuration (manifest.yml, deployment YAML, or network policies) to see if the broker service is accessible from external networks or the public internet
    Affected if broker is externally accessible without network-level authentication
  4. Verify authentication endpoint accessibility
    Examine whether the broker authentication endpoint accepts unauthenticated requests from untrusted networks by reviewing firewall rules, route configuration, or API gateway settings
    Affected if authentication endpoint is reachable from untrusted networks

You are affected if your Broker API version is below 3.0.2 or your On Demand Services SDK is below 0.24.0 and the broker is network-accessible, as this allows remote attackers to perform brute-force credential attacks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 0.24.0 / 3.0.2 or later
Fixed in 0.24.03.0.2
Interim mitigation

Upgrade the On Demand Services SDK to version 0.24 or later which contains the fixed credential verification method.

Recommended fix High confidence

Broker Api: 3.0.2 | On Demand Services Sdk: 0.24.0

  1. 1. Identify all deployments using the Pivotal Cloud Foundry On Demand Services SDK version below 0.24.0
  2. 2. Identify all deployments using the Broker Api component version below 3.0.2
  3. 3. Upgrade the On Demand Services SDK to version 0.24.0 or later
  4. 4. Upgrade the Broker Api to version 3.0.2 or later
  5. 5. After upgrading, verify that the service broker is functioning correctly and that authentication behaves as expected
  6. 6. Review broker logs to ensure no unauthorized access occurred prior to the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Broker Api Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-15759 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-15759 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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