Angular: Denial of Service (DoS) via OOM in Date Formatting (formatDate)
angular
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @angular/common npm |
|
|
angular
| 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 22.0.1, 21.2.17, and 20.3.25, a Denial of Service (DoS) vulnerability exists in the @angular/common package of the Angular framework. The formatDate function, which is also utilized by the standard Angular DatePipe, does not properly limit or validate the length of the format parameter. When parsing a maliciously crafted, excessively long date format string (e.g., a repeating pattern or very large string), the internal parser splits the string iteratively using a regular expression loop. This results in uncontrolled resource consumption (high CPU utilization and excessive memory allocations), leading to a Denial of Service (DoS). This vulnerability is fixed in 22.0.1, 21.2.17, and 20.3.25.
From the CVE record · GitHub_M
The @angular/common formatDate function, also used by DatePipe, does not limit the length of date format strings. If an attacker can supply an excessively long format string to that function, parsing can consume excessive CPU and memory, causing a denial of service. The input does not specify whether this requires network access, authentication, or user interaction.
Teams using npm @angular/common in the affected ranges (>=22.0.0-next.0 <22.0.1, >=21.0.0-next.0 <21.2.17, >=20.0.0-next.0 <20.3.25, or <=19.2.25) should check their installations.