Timing attack allows extraction of signing key in Bits Service

published 2018-12-10 7y ago modified 2026-06-17 4mo ago also EUVD-2018-7661

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

Cloud Foundry Bits Service, versions prior to 2.18.0, includes an information disclosure vulnerability. A remote malicious user may execute a timing attack to brute-force 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.18.0

Is CVE-2018-15800 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.93% chance of exploitation in the next 30 days, higher than 60% 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	6.8	CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
NVD	2.0	3.5	AV:N/AC:M/Au:S/C:P/I:N/A:N

Affected products

Cloud Foundry Bits Service Release

Classification

Weakness

CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

cloudfoundry.org /blog/cve-2018-15800
mitigation, vendor-advisory

Sources

CVE List CVE-2018-15800
NVD CVE-2018-15800

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.