Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven📦 npm
Not in CISA KEV
HIGH severity

CVE-2024-21490

HIGH

CVE-2024-21490 is a high-severity (CVSS 7.5) CWE-1333 vulnerability in org.webjars.npm:angular. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2024-21490 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

angular vulnerable to super-linear runtime due to backtracking

Also known asGHSA-4w4v-5hc9-xrr2
Published
Feb 10, 2024
Updated
Mar 15, 2026
Affected
3 pkgs
Patched
None yet
Exploits
1 known
Exploitation data as of Mar 15, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

3 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

angularnpm
693Kdownloads / week

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 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.

Affected Packages

3 total
EcosystemPackageVulnerable rangeFix
Mavenorg.webjars.npm:angular1.3.0No fix
Mavenorg.webjars.bower:angular1.3.0No fix
📦npmangular1.3.0No fix
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.webjars.npm:angular. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of org.webjars.npm:angular has shipped for CVE-2024-21490 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2024-21490 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2024-21490. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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 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](https://www.npmjs.com/package/@angular/core).
O3 Security · Impact-Aware SCA

Is CVE-2024-21490 in your dependencies?

O3 detects CVE-2024-21490 across Maven, npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

CVE-2024-21490: angular Denial of Service… | O3 Security