CVE-2018-15795 json
CredHub Service Broker uses guessable client secret
published 7y ago modified 4mo ago also GHSA-q3jg-4c82-j4xh , EUVD-2018-0767
- cvss
- 8.1
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 0
- none known
Summary
Pivotal CredHub Service Broker, versions prior to 1.1.0, uses a guessable form of random number generation in creating service broker's UAA client. A remote malicious user may guess the client secret and obtain or modify credentials for users of the CredHub Service.
Patch / fix
- maven org.springframework.credhub:spring-credhub-core 1.1.0
- Pivotal Cloud Foundry CredHub Service Broker 1.1.0
Is CVE-2018-15795 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.30% chance of exploitation in the next 30 days, higher than 70% 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:A/AC:L/PR:H/UI:N/S:C/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 |
| GitHub | 3.0 | 8.1 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.springframework.credhub:spring-credhub-core | <1.1.0 |
1.1.0 |
Affected products
- Pivotal Cloud Foundry CredHub Service Broker
Classification
- Weakness
-
- CWE-338 Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
References
-
pivotal.io
/security/cve-2018-15795
web, mitigation, vendor-advisory
-
securityfocus.com
/bid/105915
vdb-entry, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2018-15795
advisory
-
github.com
/advisories/GHSA-q3jg-4c82-j4xh
advisory
Sources
- CVE List CVE-2018-15795
- GitHub Advisory GHSA-q3jg-4c82-j4xh
- NVD CVE-2018-15795
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.