HistoryEdit

RUSTSEC-2021-0128

Incorrect Lifetime Bounds on Closures in rusqlite

Issued
Package
rusqlite (crates.io)
Type
Vulnerability
Categories
Keywords
#use-after-free #incorrect-lifetime
Details
https://github.com/rusqlite/rusqlite/issues/1048
Patched
  • >=0.26.2
  • ^0.25.4
Unaffected
  • <0.25.0
Affected Functions
Version
rusqlite::Connection::commit_hook
  • >=0.25.0, <0.25.4
  • >=0.26.0, <0.26.2
rusqlite::Connection::create_aggregate_function
  • >=0.25.0, <0.25.4
  • >=0.26.0, <0.26.2
rusqlite::Connection::create_collation
  • >=0.25.0, <0.25.4
  • >=0.26.0, <0.26.2
rusqlite::Connection::create_scalar_function
  • >=0.25.0, <0.25.4
  • >=0.26.0, <0.26.2
rusqlite::Connection::create_window_function
  • >=0.25.0, <0.25.4
  • >=0.26.0, <0.26.2
rusqlite::Connection::rollback_hook
  • >=0.25.0, <0.25.4
  • >=0.26.0, <0.26.2
rusqlite::Connection::update_hook
  • >=0.25.0, <0.25.4
  • >=0.26.0, <0.26.2

Description

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:

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.