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.
This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.
rocket_contrib(28 total, 19 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| diesel ⚠️ | ^1.0 | 2.1.5 | out of date |
| glob | ^0.3 | 0.3.1 | up to date |
| handlebars | ^1.0 | 5.1.2 | out of date |
| log | ^0.4 | 0.4.21 | up to date |
| memcache | ^0.11 | 0.17.2 | out of date |
| mongodb | ^0.3.12 | 2.8.2 | out of date |
| mysql | ^14 | 25.0.0 | out of date |
| notify | ^4.0.6 | 6.1.1 | out of date |
| postgres | ^0.15 | 0.19.7 | out of date |
| r2d2 | ^0.8 | 0.8.10 | up to date |
| r2d2-memcache | ^0.3 | 0.6.0 | out of date |
| r2d2-mongodb | ^0.2.0 | 0.2.2 | up to date |
| r2d2_cypher | ^0.4 | 0.4.0 | up to date |
| r2d2_mysql | ^9 | 24.0.0 | out of date |
| r2d2_postgres | ^0.14 | 0.18.1 | out of date |
| r2d2_redis | ^0.8 | 0.14.0 | out of date |
| r2d2_sqlite | ^0.6 | 0.24.0 | out of date |
| redis | ^0.9 | 0.25.3 | out of date |
| rmp-serde | ^0.13 | 1.2.0 | out of date |
| rocket | ^0.4.10 | 0.5.0 | out of date |
| rocket_contrib_codegen | ^0.4.10 | 0.4.11 | up to date |
| rusqlite ⚠️ | ^0.14.0 | 0.31.0 | out of date |
| rusted_cypher | ^1 | 1.1.0 | up to date |
| serde | ^1.0 | 1.0.198 | up to date |
| serde_json | ^1.0.26 | 1.0.116 | up to date |
| tera | ^0.11 | 1.19.1 | out of date |
| time ⚠️ | ^0.1.40 | 0.3.36 | out of date |
| uuid | ^0.7 | 1.8.0 | out of date |
rusqlite: Various memory safety issuesSeveral 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.
time: Potential segfault in the time crateUnix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.
The affected functions from time 0.2.7 through 0.2.22 are:
time::UtcOffset::local_offset_attime::UtcOffset::try_local_offset_attime::UtcOffset::current_local_offsettime::UtcOffset::try_current_local_offsettime::OffsetDateTime::now_localtime::OffsetDateTime::try_now_localThe affected functions in time 0.1 (all versions) are:
atat_utcnowNon-Unix targets (including Windows and wasm) are unaffected.
Pending a proper fix, the internal method that determines the local offset has been modified to always return None on the affected operating systems. This has the effect of returning an Err on the try_* methods and UTC on the non-try_* methods.
Users and library authors with time in their dependency tree should perform cargo update, which will pull in the updated, unaffected code.
Users of time 0.1 do not have a patch and should upgrade to an unaffected version: time 0.2.23 or greater or the 0.3 series.
A possible workaround for crates affected through the transitive dependency in chrono, is to avoid using the default oldtime feature dependency of the chrono crate by disabling its default-features and manually specifying the required features instead.
Cargo.toml:
chrono = { version = "0.4", default-features = false, features = ["serde"] }
chrono = { version = "0.4.22", default-features = false, features = ["clock"] }
Commandline:
cargo add chrono --no-default-features -F clock
Sources:
diesel: Fix a use-after-free bug in diesels Sqlite backendWe've misused sqlite3_column_name. The
SQLite documentation
states that the following:
The returned string pointer is valid until either the prepared statement is destroyed by sqlite3_finalize() or until the statement is automatically reprepared by the first call to sqlite3_step() for a particular run or until the next call to sqlite3_column_name() or sqlite3_column_name16() on the same column.
As part of our query_by_name infrastructure we've first received all
field names for the prepared statement and stored them as string slices
for later use. After that we called sqlite3_step() for the first time,
which invalids the pointer and therefore the stored string slice.