Skip to content

angular vulnerable to super-linear runtime due to backtracking

High severity GitHub Reviewed Published Feb 10, 2024 to the GitHub Advisory Database • Updated May 14, 2024

Package

npm angular (npm)

Affected versions

>= 1.3.0, <= 1.8.3

Patched versions

None
maven org.webjars.bower:angular (Maven)
>= 1.3.0, <= 1.8.3
None
maven org.webjars.npm:angular (Maven)
>= 1.3.0, <= 1.8.3
None

Description

This affects versions of the package angular from 1.3.0. A regular expression used to split the value of the ng-srcset directive is vulnerable to super-linear runtime due to backtracking. With a large carefully-crafted input, this can result in catastrophic backtracking and cause a denial of service.

Note:

This package is EOL and will not receive any updates to address this issue. Users should migrate to @angular/core.

References

Published by the National Vulnerability Database Feb 10, 2024
Published to the GitHub Advisory Database Feb 10, 2024
Reviewed Feb 13, 2024
Last updated May 14, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.052%
(21st percentile)

Weaknesses

CVE ID

CVE-2024-21490

GHSA ID

GHSA-4w4v-5hc9-xrr2

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.