rusqlite
Affected
- introduced
0.25.0, fixed0.25.4(semver)
Fixed versions
0.25.4
Fix
- Fixed version
0.25.4cargo update -p rusqlite --precise 0.25.4
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-87xh-9q6h-r5cc, GHSA-92cx-4xm7-jr9m, GHSA-cm8g-544f-p9x9, GHSA-f6f2-3w33-54r9, GHSA-g4g4-3pqw-8m7f, GHSA-g87r-23vw-7f87, GHSA-q89g-4vhh-mvvm, RUSTSEC-2021-0128
Use After Free in rusqlite
An issue was discovered in the rusqlite crate 0.25.x before 0.25.4 and 0.26.x before 0.26.2 for Rust. commit_hook has a use-after-free.
High Basis: The source's own band: HIGH
0.25.0, fixed 0.25.4 (semver)0.25.4
0.25.4cargo update -p rusqlite --precise 0.25.40.26.0, fixed 0.26.2 (semver)0.26.2
0.26.2cargo update -p rusqlite --precise 0.26.2Fix 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