rusqlite
Affected
- introduced
0.26.0, fixed0.26.2(semver)
Fixed versions
0.26.2
Fix
- Fixed version
0.26.2cargo update -p rusqlite --precise 0.26.2
Advisory
Also known as: CVE-2021-45713, CVE-2021-45714, CVE-2021-45715, CVE-2021-45716, CVE-2021-45717, CVE-2021-45718, CVE-2021-45719, GHSA-4qr3-m7ww-hh9g, GHSA-87xh-9q6h-r5cc, GHSA-92cx-4xm7-jr9m, GHSA-cm8g-544f-p9x9, GHSA-f6f2-3w33-54r9, GHSA-g4g4-3pqw-8m7f, GHSA-g87r-23vw-7f87, RUSTSEC-2021-0128
Incorrect Lifetime Bounds on Closures in rusqlite
The lifetime bound on several closure-accepting rusqlite functions (specifically, functions which register a callback to be later invoked by SQLite) was too relaxed. If a closure referencing borrowed values on the stack is was passed to one of these functions, it could allow Rust code to access objects on the stack after they have been dropped.
The impacted functions are:
cfg(feature = "functions"): Connection::create_scalar_function, Connection::create_aggregate_function and Connection::create_window_function.cfg(feature = "hooks"): Connection::commit_hook, Connection::rollback_hook and Connection::update_hook.cfg(feature = "collation"): Connection::create_collation.The issue exists in all 0.25.* versions prior to 0.25.4, and all 0.26.* versions prior to 0.26.2 (specifically: 0.25.0, 0.25.1, 0.25.2, 0.25.3, 0.26.0, and 0.26.1).
The fix is available in versions 0.26.2 and newer, and also has been back-ported to 0.25.4. As it does not exist in 0.24.*, all affected versions should have an upgrade path to a semver-compatible release.
High Basis: The source's own band: HIGH
0.26.0, fixed 0.26.2 (semver)0.26.2
0.26.2cargo update -p rusqlite --precise 0.26.20.25.0, fixed 0.25.4 (semver)0.25.4
0.25.4cargo update -p rusqlite --precise 0.25.4Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0