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 mongodb

Dependencies

(19 total, 13 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 bitflags^1.0.02.6.0out of date
 bson^0.13.02.13.0out of date
 bufstream^0.1.30.1.4up to date
 byteorder^1.0.01.5.0up to date
 chrono ⚠️^0.4.00.4.38maybe insecure
 clippy~00.0.302up to date
 data-encoding^2.0.02.6.0up to date
 hex^0.3.20.4.3out of date
 hmac^0.6.20.12.1out of date
 md-5^0.7.00.10.6out of date
 openssl ⚠️^0.10.150.10.66maybe insecure
 pbkdf2^0.2.00.12.2out of date
 rand^0.3.150.8.5out of date
 scan_fmt^0.1.10.2.6out of date
 semver^0.8.01.0.23out of date
 separator^0.3.10.4.1out of date
 sha-1^0.7.00.10.1out of date
 textnonce^0.6.31.0.0out of date
 time ⚠️^0.1.370.3.36out of date

Dev dependencies

(4 total, 1 outdated)

CrateRequiredLatestStatus
 approx^0.1.10.5.1out of date
 serde^1.0.691.0.210up to date
 serde_derive^1.0.691.0.210up to date
 serde_json^1.0.31.0.128up to date

Security Vulnerabilities

time: Potential segfault in the time crate

RUSTSEC-2020-0071

Impact

The affected functions set environment variables without synchronization. On Unix-like operating systems, this can crash in multithreaded programs. Programs may segfault due to dereferencing a dangling pointer if an environment variable is read in a different thread than the affected functions. This may occur without the user's knowledge, notably in the Rust standard library or third-party libraries.

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:

  • time::at_utc
  • time::at
  • time::now
  • time::tzset

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

openssl: `MemBio::get_buf` has undefined behavior with empty buffers

RUSTSEC-2024-0357

Previously, MemBio::get_buf called slice::from_raw_parts with a null-pointer, which violates the functions invariants, leading to undefined behavior. In debug builds this would produce an assertion failure. This is now fixed.