22.0.4
10 years ago
4 days ago
Known vulnerabilities in the @angular/common package. This does not include vulnerabilities belonging to this package’s dependencies.
Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.
Fix for free| Vulnerability | Vulnerable Version |
|---|---|
Affected versions of this package are vulnerable to Use of Weak Hash due to the use of a weak 32-bit hash in the How to fix Use of Weak Hash? Upgrade | <20.3.25>=21.0.0-next.0 <21.2.17>=22.0.0-next.0 <22.0.1 |
Affected versions of this package are vulnerable to Use of Cache Containing Sensitive Information via the Note: This is only exploitable if server-side rendering and hydration are enabled, credentialed HTTP requests are performed during SSR, and the SSR-rendered HTML is cached by a shared caching layer without proper cache-control headers to distinguish authenticated users. How to fix Use of Cache Containing Sensitive Information? Upgrade | <19.2.23>=20.0.0-next.0 <20.3.22>=21.0.0-next.0 <21.2.15>=22.0.0-next.0 <22.0.0-rc.2 |
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) via the Note: This is only exploitable if the application formats dates using the vulnerable utility or pipe and the format string is customizable or controlled by untrusted user input. How to fix Regular Expression Denial of Service (ReDoS)? Upgrade | <20.3.25>=21.0.0-next.0 <21.2.17>=22.0.0-next.0 <22.0.1 |
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via the Note: This is only exploitable if the application uses number formatting utilities and allows untrusted input to control the How to fix Allocation of Resources Without Limits or Throttling? Upgrade | <19.2.23>=20.0.0-next.0 <20.3.22>=21.0.0-next.0 <21.2.15>=22.0.0-next.0 <22.0.0-rc.2 |
Affected versions of this package are vulnerable to Insertion of Sensitive Information Into Sent Data via the Note: This is only exploitable if XSRF protection is enabled and the application allows requests to protocol-relative URLs. How to fix Insertion of Sensitive Information Into Sent Data? Upgrade | <19.2.16>=20.0.0-next.0 <20.3.14>=21.0.0-next.0 <21.0.1 |