Vulnerability CriticalRUSTSEC-2020-0014 · rusqlite
RUSTSEC-2020-0014: Various memory safety issues
Short answerA security vulnerability in the rusqlite crate: Various memory safety issues. GitHub rates it Critical. Fixed in 0.23.0: update to a fixed version.
| Crate | rusqlite |
|---|---|
| Type | Vulnerability |
| Affected versions | Before 0.23.0. |
| Fixed in | 0.23.0 |
| Severity | Critical (GitHub rating) |
| Published | 2020-04-23 |
| Last changed | 2024-03-15 |
| Also known as | CVE-2020-35866, CVE-2020-35867, CVE-2020-35868, CVE-2020-35869, CVE-2020-35870, CVE-2020-35871, CVE-2020-35872, CVE-2020-35873, GHSA-28ph-f7gx-fqj8, GHSA-3cgf-9m6x-pwwr, GHSA-6q5w-m3c5-rv95, GHSA-8h4j-vm3r-vcq3, GHSA-8r7q-r9mx-35rh, GHSA-g4w7-3qr8-5623, GHSA-q3cc-7p7g-392c, GHSA-rjh8-p66p-jrh5 |
| Affected functions | rusqlite::Connection::get_aux, rusqlite::Connection::set_aux, rusqlite::session::Session::attach, rusqlite::session::Session::diff, rusqlite::trace::log, rusqlite::vtab::create_module |
What to do
- See which version you have:
cargo tree -i rusqlite(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p rusqlite. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplerusqlite = "0.23.0") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
Several memory safety issues have been uncovered in an audit of rusqlite.
See https://github.com/rusqlite/rusqlite/releases/tag/0.23.0 for a complete list.
References
- Package: crates.io/crates/rusqlite
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0014.html
- Web: github.com/rusqlite/rusqlite/releases/tag/0.23.0
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Other advisories for rusqlite
Up next
Same craterusqlite: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?