Vulnerability in sqlite3 (CVE-2022-43441)
Summary
Vulnerability in sqlite3 (CVE-2022-43441). Successful exploitation can lead to full system takeover. Exploitable via sqlite3. Mitigation: upgrade to 5.1.5 or later.
Original description
The description as published by the source.
A code execution vulnerability exists in the Statement Bindings functionality of Ghost Foundation node-sqlite3 5.1.1. A specially-crafted Javascript file can lead to arbitrary code execution. An attacker can provide malicious input to trigger this vulnerability.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2022-43441 has been found in sqlite3.
Attackers can target a specific entry point like sqlite3 over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: upgrade sqlite3 to 5.1.5 or later.
If unsure, ask your IT team or search "sqlite3 CVE-2022-43441" on the vendor's site.
CVE-2022-43441 (sqlite3) — CWE-913
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: sqlite3
Patched: 5.1.5 — apply immediately
Workaround: * Ensure there is sufficient sanitization in the parent application to protect against invalid values being supplied to binding parameters.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-913) exists in sqlite3. Attackers reach the vulnerable code path via sqlite3 without authentication.
Check the vendor advisory for the affected versions of sqlite3. Attack surface: sqlite3.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 5.1.5.
Workaround: * Ensure there is sufficient sanitization in the parent application to protect against invalid values being supplied to binding parameters.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'sqlite3' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'sqlite3' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
sqlite3を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
* Ensure there is sufficient sanitization in the parent application to protect against invalid values being supplied to binding parameters.パッチが適用されるまでの応急処置として、* Ensure there is sufficient sanitization in the parent application to protect against invalid values being supplied to binding parameters. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade sqlite3 to 5.1.5ステージング環境で 5.1.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2022-43441 node-sqlite3 Fixed in: 5.0.0+ds1-1+deb11u2
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web talosintelligence.com
- web talosintelligence.com