Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning
angular · @angular common
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @angular/common npm |
|
|
angular · @angular common
| Product | Affected | Fixed in |
|---|---|---|
| @angular/common npm |
|
|
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.
From the CVE record · GitHub_M
In affected @angular/common versions, HttpTransferCache comma-joins repeated request parameters, allowing distinct HttpClient requests to share a transfer-cache key. This can cause reuse of the wrong backend response. The input does not specify attacker access, authentication requirements, or user interaction.
Teams running @angular/common should check versions >=22.0.0-next.0 <22.0.2, >=21.0.0-next.0 <21.2.19, >=20.0.0-next.0 <20.3.27, or <=19.2.25.