CVE-2018-15796
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 Bits Service Release, versions prior to 2.14.0, uses an insecure hashing algorithm to sign URLs. A remote malicious user may obtain a signed URL and extract the signing key, allowing them complete read and write access to the the Bits Service storage.
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 Bits Service Release versions prior to 2.14.0 use an insecure hashing algorithm for URL signing. An attacker who obtains a signed URL can extract the signing key from it due to the weak cryptographic construction, enabling complete read and write access to the service's storage backend.
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.14.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.
-
Identify Bits Service deployment versionRun 'bosh deployments' or check your Cloud Foundry deployment manifests to locate the bits-service release version. If using the cf CLI, check the service broker information.Affected if The installed version is prior to 2.14.0
-
Verify Bits Service is runningCheck running instances with 'bosh instances' or via the Cloud Foundry API endpoint /v2/services. Confirm the bits-service job is deployed and active.Affected if Bits Service is deployed and running a vulnerable version < 2.14.0
-
Check if signed URL generation is enabledReview the Bits Service configuration (typically in the manifest or ops manager) for the 'signing_key' or 'url_signing' settings. Look for whether the service is configured to generate signed download/upload URLs.Affected if Signed URLs are enabled and the service version is < 2.14.0
-
Inspect active signing key materialExamine the bits-service manifest or deployed configuration files for the signing key. If the key appears to be used with a weak HMAC construction (e.g., MD5 or truncated SHA), the vulnerability applies.Affected if A signing key is configured and the service version is < 2.14.0
Your environment is affected if the Cloud Foundry Bits Service is deployed at a version earlier than 2.14.0 and signed URLs are in use.
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.14.0
Upgrade Cloud Foundry Bits Service to version 2.14.0 or later which implements a secure signing mechanism. Additionally, rotate any signing keys that may have been exposed.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15796 — 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-15796 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