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

GHSA-9qrh-qjmc-5w2p

HIGH

GHSA-9qrh-qjmc-5w2p is a high-severity (CVSS 7.5) vulnerability in sqlite3. O3 Security confirms whether GHSA-9qrh-qjmc-5w2p is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Denial-of-Service when binding invalid parameters in sqlite3

Also known asCVE-2022-21227
Published
Apr 28, 2022
Updated
Jan 14, 2025
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

sqlite3npm
2.6Mdownloads / week

Description

Affected versions of sqlite3 will experience a fatal error when supplying a specific object in the parameter array. This error causes the application to crash and could not be caught. Users of sqlite3 v5.0.0, v5.0.1 and v5.0.2 are affected by this. This issue is fixed in v5.0.3. All users are recommended to upgrade to v5.0.3 or later. Ensure there is sufficient sanitization in the parent application to protect against invalid values being supplied to binding parameters as a workaround.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmsqlite35.0.0&&< 5.0.35.0.3

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sqlite3. 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 sqlite3 to 5.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9qrh-qjmc-5w2p 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 GHSA-9qrh-qjmc-5w2p 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-9qrh-qjmc-5w2p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Affected versions of sqlite3 will experience a fatal error when supplying a specific object in the parameter array. This error causes the application to crash and could not be caught. Users of `sqlite3` v5.0.0, v5.0.1 and v5.0.2 are affected by this. This issue is fixed in v5.0.3. All users are recommended to upgrade to v5.0.3 or later. Ensure there is sufficient sanitization in the parent application to protect against invalid values being supplied to binding parameters as a workaround.
O3 Security · Impact-Aware SCA

Is GHSA-9qrh-qjmc-5w2p in your dependencies?

O3 detects GHSA-9qrh-qjmc-5w2p across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.