Credential exposure to space supporter
- 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 v60.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: total
Summary
This vulnerability affects Cloud Foundry, a platform for deploying and managing applications, where a user with the SpaceSupporter role can improperly change an application's start command or buildpack despite lacking the SpaceDeveloper privileges required for those actions. The flaw allows such a user to escalate privileges and gain unauthorized access to service credentials.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
A SpaceSupporter could improperly modify an application's start command and buildpack—actions requiring SpaceDeveloper privileges. This privilege escalation enables unauthorized retrieval of service credentials through malicious start commands or custom buildpacks.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Cloud Foundry Cloud Foundry Controller (CAPI)
through 1.247.0
- Cloud Foundry cf-deployment
fixed in v60.9.0