DoS Vulnerability in UAA Related to JWKS URI Handling
- 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 79.9.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
The User Account and Authentication (UAA) service, used for identity management in Cloud Foundry deployments, is affected by this vulnerability. An attacker can exploit the private_key_jwt client-authentication feature to cause excessive CPU usage and memory exhaustion, making the service unavailable.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
A denial-of-service vulnerability exists in UAA's private_key_jwt client-authentication mechanism. When UAA retrieves a remote JWKS URI, it caches the response. Invalid authentication attempts can trigger full deserialization of this cached data. An attacker with prerequisites (write access to clients or a compromised endpoint) can send anonymous requests that force repeated parsing of large cached objects, causing excessive CPU usage and potential Java heap exhaustion via OutOfMemoryError, resulting in service unavailability.
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 UAA
From 76.23.0 · fixed in 79.9.0
- Cloud Foundry cf-deployment
fixed in 60.11.0