Angular: Information Leak via Default Caching of Credentialed Requests in HttpTransferCache
- Published
- 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 22.0.0-rc.2, 21.2.15, 20.3.22, 19.2.23
- 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
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.23, a vulnerability was discovered in @angular/common when Server-Side Rendering (SSR) and hydration are enabled. The HttpTransferCache utility optimizes hydration by caching outgoing HTTP requests performed during SSR and transferring the cached state to the client-side application via TransferState. However, the caching mechanism fails to inspect the withCredentials flag or the Cookie header of outgoing requests. As a result, credentialed, user-specific responses may be cached by default in the shared TransferState payload. When these responses are serialized into the HTML, any caching layer (such as a CDN, reverse proxy, or shared server cache) that caches the SSR-rendered HTML page could inadvertently cache and leak one user's private data to other users, leading to a high-severity information disclosure vulnerability. This vulnerability is fixed in 22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.23.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- angular angular
From 22.0.0-next.0 · fixed in 22.0.0-rc.2; From 21.0.0-next.0 · fixed in 21.2.15; From 20.0.0-next.0 · fixed in 20.3.22; From 19.0.0-next.0 · fixed in 19.2.23; through 18.2.14
- @angular/commonnpm
From 22.0.0-next.0 · fixed in 22.0.0-rc.2
- @angular/commonnpm
From 20.0.0-next.0 · fixed in 20.3.22
- @angular/commonnpm
From 19.0.0-next.0 · fixed in 19.2.23
- @angular/commonnpm
through 18.2.14
- @angular/commonnpm
From 21.0.0-next.0 · fixed in 21.2.15