Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

CVE-2022-21222

MEDIUM

CVE-2022-21222 is a medium-severity (CVSS 5.3) CWE-1333 vulnerability in css-what. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2022-21222 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Regular Expression Denial of Service (ReDoS)

Also known asGHSA-p28h-cc7q-c4fg
Published
Sep 30, 2022
Updated
Jul 15, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
1 known

Real-World Exposure

1 pkg affected

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

css-whatnpm
67.8Mdownloads / week

Description

The package css-what before 2.1.3 are vulnerable to Regular Expression Denial of Service (ReDoS) due to the usage of insecure regular expression in the re_attr variable of index.js. The exploitation of this vulnerability could be triggered via the parse function.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmcss-whatall versions2.1.3
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 css-what. 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. Fix

    Update css-what to 2.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-21222 is resolved across your whole dependency graph.

  3. Workarounds

    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-2022-21222 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-2022-21222. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The package css-what before 2.1.3 are vulnerable to Regular Expression Denial of Service (ReDoS) due to the usage of insecure regular expression in the re_attr variable of index.js. The exploitation of this vulnerability could be triggered via the parse function.
O3 Security · Impact-Aware SCA

Is CVE-2022-21222 in your dependencies?

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