CVE-2018-15755
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 CF Networking Release, versions 2.11.0 prior to 2.16.0, contain an internal api endpoint vulnerable to SQL injection between Diego cells and the policy server. A remote authenticated malicious user with mTLS certs can issue arbitrary SQL queries and gain access to the policy server.
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 Cloud Foundry CF Networking Release contains a SQL injection vulnerability in the internal API endpoint of the policy server. This endpoint, which handles communication between Diego cells and the policy server, does not properly sanitize SQL queries. An authenticated attacker with valid mTLS certificates can inject arbitrary SQL statements, potentially exfiltrating data or gaining unauthorized access to the policy server database.
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.11.0, < 2.16.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
- 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.
-
Identify the CF Networking Release versionQuery your Cloud Foundry deployment's deployed releases using 'bosh releases' or your deployment manifest to obtain the exact version number of the cf-networking releaseAffected if The version falls within the range >= 2.11.0 and < 2.16.0
-
Confirm the policy server component is deployedCheck if the policy-server or policy-server-internal component is running in your Diego cells or as a BOSH job. Use 'bosh vms' or your orchestration tool to list running instances with the policy-server jobAffected if The policy server job is deployed and running in your environment
-
Verify the internal API endpoint is accessibleCheck the network configuration and routing for the policy-server-internal API. Inspect the BOSH job properties for policy-server-internal to determine if the internal API port is bound and routable between cells and the policy serverAffected if The internal API endpoint is network-accessible from Diego cells (typically on port 8080 or as defined in your deployment)
-
Confirm mTLS authentication is in useReview the policy-server-internal job configuration and confirm that mutual TLS authentication is enabled for inter-component communication between Diego cells and the policy serverAffected if mTLS is configured, which satisfies the authentication requirement for this exploit
Your environment is affected if the deployed CF Networking Release version is between 2.11.0 (inclusive) and 2.16.0 (exclusive) and the policy server internal API is accessible with mTLS authentication.
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.16.0
Upgrade CF Networking Release to version 2.16.0 or later to remediate this vulnerability. Additionally, review and rotate any credentials or certificates that may have been exposed, and audit the policy server database for signs of unauthorized access.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15755 — 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-15755 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