Signing Key Extraction in Bits Service Release

published 2018-11-09 8y ago modified 2026-06-17 4mo ago also EUVD-2018-7658

cvss: 8.1; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.7%; EPSS 0.7% chance of exploitation in 30 days, percentile 53%
public exploits: 0; none known

Cloud 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.

Patch / fix

fixed in 1

Cloud Foundry bits-service-release 2.14.0

Is CVE-2018-15796 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.71% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.0	8.1	CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
NVD	3.0	8.1	CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
NVD	2.0	5.5	AV:N/AC:L/Au:S/C:P/I:P/A:N

Affected products

Cloud Foundry bits-service-release

Classification

Weakness

CWE-326 Inadequate Encryption Strength

References

cloudfoundry.org /blog/cve-2018-15796
vendor-advisory

Sources

CVE List CVE-2018-15796
NVD CVE-2018-15796

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.