Space Developer can extract space-scoped broker credentials
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in v1.248.0, 60.9.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
The vulnerability affects the Cloud Foundry API, specifically how it manages space-scoped service brokers. A user with the SpaceDeveloper role could change the URL of such a broker while leaving its stored credentials intact, then redirect those credentials to a broker they control and thereby obtain them.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
A user with SpaceDeveloper privileges could modify the URL of a space-scoped broker without altering its credentials, enabling extraction of existing broker credentials by redirecting them to a broker under their control. The CF API does not permit direct reading of broker credentials, making this an indirect extraction method.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Cloud Foundry CAPI (Cloud Foundry Controller)
fixed in v1.248.0
- Cloud Foundry CF Deployment
fixed in 60.9.0