Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning
- 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 20.3.27, 21.2.19, 22.0.2
- 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: yes
- Technical impact: partial
Summary
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.27, 21.2.19, and 22.0.2, HttpTransferCache comma-joins repeated request parameters, allowing semantically distinct HttpClient requests to use the same transfer-cache key and reuse a wrong backend response. This issue is fixed in versions 20.3.27, 21.2.19, and 22.0.2.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- angular angular
fixed in 20.3.27; From 21.0.0-next.0 · fixed in 21.2.19; From 22.0.0-next.0 · fixed in 22.0.2
- @angular common
fixed in 20.3.27; From 21.0.0-next.0 · fixed in 21.2.19; From 22.0.0-next.0 · fixed in 22.0.2
- @angular/commonnpm
From 22.0.0-next.0 · fixed in 22.0.2
- @angular/commonnpm
From 21.0.0-next.0 · fixed in 21.2.19
- @angular/commonnpm
From 20.0.0-next.0 · fixed in 20.3.27
- @angular/commonnpm
through 19.2.25