CVE-2018-15795: Use of Cryptographically Weak PRNG in Pivotal CredHub Service Broker

Summary

29/11/2018
Yes i
High
8.1

CVE-2018-15795: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) in Pivotal CredHub Service Broker. Affects org.springframework.credhub:spring-credhub-core versions < 1.1.0. Fixed in 1.1.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

Pivotal CredHub Service Broker is a Maven package called 'org.springframework.credhub:spring-credhub-core'. It is a service broker that generates a UAA client for users of the CredHub Service. The package is vulnerable to a guessable form of random number generation, which can allow a remote malicious user to guess the client secret and obtain or modify credentials for CredHub Service users.

Vulnerability Detail

The vulnerability in Pivotal CredHub Service Broker arises from the use of a weak pseudo-random number generator (PRNG) in creating the service broker's UAA client. This makes it possible for a remote attacker to guess the client secret and gain unauthorized access to or manipulate credentials of CredHub Service users. The impact of this vulnerability can be significant, as it compromises the security and confidentiality of sensitive user data.

How To Fix

Latest published version: 4.1.0 as of 23 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.1.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. The recommended solution is to update the package to the fixed version.

Conclusion

The vulnerability in Pivotal CredHub Service Broker, caused by the use of a weak PRNG, can lead to unauthorized access to or manipulation of user credentials. It is crucial to update the package to version 1.1.0 or later to mitigate this vulnerability. For additional assistance, please reach out to DevNack.com.

See every vulnerability recorded for org.springframework.credhub:spring-credhub-core →

Share this vulnerability

FAQ

Pivotal CredHub Service Broker is a service broker that generates a UAA client for users of the CredHub Service. It is used to manage and secure credentials in cloud-native applications.

The vulnerability allows a remote attacker to guess the client secret and gain unauthorized access to or manipulate credentials of CredHub Service users.

To fix this vulnerability, update the Pivotal CredHub Service Broker package to version 1.1.0 or later.

No specific workaround is mentioned for this vulnerability. Updating the package to the fixed version is the recommended solution.

For further support on vulnerability remediation, you can contact info@devnack.com.

How To Fix

Latest published version: 4.1.0 as of 23 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.1.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback