This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate rusqlite

Dependencies

(15 total, 3 outdated, 1 insecure, 2 possibly insecure)

CrateRequiredLatestStatus
 bitflags^1.21.3.2up to date
 byteorder^1.31.4.3up to date
 chrono ⚠️^0.40.4.19insecure
 csv^1.11.1.6up to date
 fallible-iterator^0.20.2.0up to date
 fallible-streaming-iterator^0.10.1.9up to date
 hashlink^0.60.7.0out of date
 lazy_static^1.41.4.0up to date
 libsqlite3-sys^0.20.10.23.2out of date
 memchr^2.32.4.1up to date
 serde_json^1.01.0.75up to date
 smallvec ⚠️^1.01.8.0maybe insecure
 time ⚠️^0.20.3.5out of date
 url^2.12.2.2up to date
 uuid^0.80.8.2up to date

Dev dependencies

(7 total, all up-to-date)

CrateRequiredLatestStatus
 bencher^0.10.1.5up to date
 doc-comment^0.30.3.3up to date
 lazy_static^1.41.4.0up to date
 regex^1.31.5.4up to date
 tempfile^3.1.03.3.0up to date
 unicase^2.6.02.6.0up to date
 uuid^0.80.8.2up 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

No workarounds are known.

References

time-rs/time#293

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

smallvec: Buffer overflow in SmallVec::insert_many

RUSTSEC-2021-0003

A bug in the SmallVec::insert_many method caused it to allocate a buffer that was smaller than needed. It then wrote past the end of the buffer, causing a buffer overflow and memory corruption on the heap.

This bug was only triggered if the iterator passed to insert_many yielded more items than the lower bound returned from its size_hint method.

The flaw was corrected in smallvec 0.6.14 and 1.6.1, by ensuring that additional space is always reserved for each item inserted. The fix also simplified the implementation of insert_many to use less unsafe code, so it is easier to verify its correctness.

Thank you to Yechan Bae (@Qwaz) and the Rust group at Georgia Tech’s SSLab for finding and reporting this bug.