CVE-2022-35737 — libsqlite3-sys
HIGHCVE-2022-35737 is a high-severity (CVSS 7.5) CWE-129 vulnerability in libsqlite3-sys. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for libsqlite3-sys — see the affected versions and patch details below.
`libsqlite3-sys` via C SQLite improperly validates array index
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-35737.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
libsqlite3-sysReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
SQLite 1.0.12 through 3.39.x before 3.39.2 sometimes allows an array-bounds overflow if billions of bytes are used in a string argument to a C API.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | libsqlite3-sys | all versions | 0.25.1cargo update -p libsqlite3-sys --precise 0.25.1 |
Affected Products
ontap select deploy administration utilitynetappuniversal forwardersplunksqlitesqliteResearch 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 libsqlite3-sys, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update libsqlite3-sys to 0.25.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-35737 is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 8 | sqlite-0:3.26.0-17.el8_7 | RHSA-2023:0110 |
| Red Hat Enterprise Linux 8.6 Extended Update Support | sqlite-0:3.26.0-16.el8_6.1 | RHSA-2024:0425 |
| Red Hat Enterprise Linux 9 | sqlite-0:3.34.1-6.el9_1 | RHSA-2023:0339 |
Frequently Asked Questions
Is CVE-2022-35737 in your dependencies?
Find it across crates.io, including transitive dependencies.