Cloud Controller exposes secrets in audit log
- 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.249.0, 60.11.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
Cloud Controller (CAPI), the control plane component of Cloud Foundry, is affected. It writes sensitive values such as custom buildpack credentials, syslog drain URL credentials, and service binding parameters into audit log events, so anyone with access to those audit logs could see secrets they should not be able to read.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Cloud Controller (CAPI) leaks sensitive data into audit logs in multiple instances: custom buildpack credentials are exposed in audit events for app manifest application, creation, and updates; syslog drain URL credentials are exposed in user-provided service instance audit events; and service binding parameters are leaked in app manifest and service binding audit events.
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 Foundation CAPI (Cloud Foundry Controller)
fixed in v1.249.0
- Cloud Foundry Foundation cf-deployment
fixed in 60.11.0