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 diesel

Dependencies

(19 total, 11 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 bigdecimal>=0.0.10, <0.2.00.4.3out of date
 bitflags^1.02.5.0out of date
 byteorder^1.01.5.0up to date
 chrono ⚠️^0.40.4.37maybe insecure
 diesel_derives~1.4.02.1.3out of date
 ipnetwork>=0.12.2, <0.19.00.20.0out of date
 libc^0.2.00.2.153up to date
 libsqlite3-sys ⚠️>=0.8.0, <0.23.00.28.0out of date
 mysqlclient-sys>=0.1.0, <0.3.00.2.5up to date
 num-bigint>=0.1.41, <0.30.4.4out of date
 num-integer>=0.1.33, <0.30.1.46up to date
 num-traits>=0.1.37, <0.30.2.18up to date
 pq-sys>=0.3.0, <0.5.00.5.0out of date
 quickcheck^0.41.0.3out of date
 r2d2>=0.8, <0.90.8.10up to date
 serde_json>=0.8.0, <2.01.0.115up to date
 time ⚠️^0.10.3.36out of date
 url^1.4.02.5.0out of date
 uuid>=0.7.0, <0.9.01.8.0out of date

Dev dependencies

(4 total, 3 outdated)

CrateRequiredLatestStatus
 cfg-if^0.1.01.0.0out of date
 dotenv>=0.8, <0.110.15.0out of date
 quickcheck^0.41.0.3out of date
 tempdir^0.3.40.3.7up to date

Security Vulnerabilities

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:

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

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.

Workarounds

No workarounds are known.

References

libsqlite3-sys: `libsqlite3-sys` via C SQLite CVE-2022-35737

RUSTSEC-2022-0090

It was sometimes possible for SQLite versions >= 1.0.12, < 3.39.2 to allow an array-bounds overflow when large string were input into SQLite's printf function.

As libsqlite3-sys bundles SQLite, it is susceptible to the vulnerability. libsqlite3-sys was updated to bundle the patched version of SQLite here.