CVE-2022-2421
CRITICALCVE-2022-2421 is a critical-severity (CVSS 10) SQL Injection vulnerability in socket.io-parser. O3 Security confirms whether CVE-2022-2421 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Socket.io - Improper type validation in attachment parsing
Blast Radius
socket.io-parser📦socket.io-parser📦socket.io-parser📦socket.io-parserReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.
Description
Due to improper type validation in attachment parsing the Socket.io js library, it is possible to overwrite the _placeholder object which allows an attacker to place references to functions at arbitrary places in the resulting query object.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | socket.io-parser | ≥ 4.0.0&&< 4.0.5 | 4.0.5 |
| 📦npm | socket.io-parser | ≥ 4.1.0&&< 4.2.1 | 4.2.1 |
| 📦npm | socket.io-parser | all versions | 3.3.3 |
| 📦npm | socket.io-parser | ≥ 3.4.0&&< 3.4.2 | 3.4.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for socket.io-parser. 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.
Fix
Update socket.io-parser to 4.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-2421 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether CVE-2022-2421 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-2421. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-2421 in your dependencies?
O3 detects CVE-2022-2421 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.