GHSA-4w4v-5hc9-xrr2
HIGHGHSA-4w4v-5hc9-xrr2 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 GHSA-4w4v-5hc9-xrr2 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
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
angularnpmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.webjars.npm:angular | ≥ 1.3.0 | No fix |
| ☕Maven | org.webjars.bower:angular | ≥ 1.3.0 | No fix |
| 📦npm | angular | ≥ 1.3.0 | No fix |
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 dependencyDetect
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.
Remediation status
No patched version of org.webjars.npm:angular has shipped for GHSA-4w4v-5hc9-xrr2 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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.
How O3 protects you
O3 pinpoints whether GHSA-4w4v-5hc9-xrr2 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 GHSA-4w4v-5hc9-xrr2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-4w4v-5hc9-xrr2 in your dependencies?
O3 detects GHSA-4w4v-5hc9-xrr2 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.