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.

Crate rocket_contrib

Dependencies

(28 total, 19 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 diesel ⚠️^1.02.1.5out of date
 glob^0.30.3.1up to date
 handlebars^1.05.1.2out of date
 log^0.40.4.21up to date
 memcache^0.110.17.2out of date
 mongodb^0.3.122.8.2out of date
 mysql^1425.0.0out of date
 notify^4.0.66.1.1out of date
 postgres^0.150.19.7out of date
 r2d2^0.80.8.10up to date
 r2d2-memcache^0.30.6.0out of date
 r2d2-mongodb^0.2.00.2.2up to date
 r2d2_cypher^0.40.4.0up to date
 r2d2_mysql^924.0.0out of date
 r2d2_postgres^0.140.18.1out of date
 r2d2_redis^0.80.14.0out of date
 r2d2_sqlite^0.60.24.0out of date
 redis^0.90.25.3out of date
 rmp-serde^0.131.1.2out of date
 rocket^0.4.110.5.0out of date
 rocket_contrib_codegen^0.4.110.4.11up to date
 rusqlite ⚠️^0.14.00.31.0out of date
 rusted_cypher^11.1.0up to date
 serde^1.01.0.197up to date
 serde_json^1.0.261.0.115up to date
 tera^0.111.19.1out of date
 time ⚠️^0.1.400.3.36out of date
 uuid^0.71.8.0out of date

Security Vulnerabilities

rusqlite: Various memory safety issues

RUSTSEC-2020-0014

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.

time: Potential segfault in the time crate

RUSTSEC-2020-0071

Impact

Unix-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_at
  • time::UtcOffset::try_local_offset_at
  • time::UtcOffset::current_local_offset
  • time::UtcOffset::try_current_local_offset
  • time::OffsetDateTime::now_local
  • time::OffsetDateTime::try_now_local

The affected functions in time 0.1 (all versions) are:

  • at
  • at_utc
  • now

Non-Unix targets (including Windows and wasm) are unaffected.

Patches

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.

Workarounds

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.

Examples:

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 backend

RUSTSEC-2021-0037

We'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.