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

Crate kelvin

Dependencies

(17 total, 9 outdated, 2 insecure)

CrateRequiredLatestStatus
 appendix ⚠️^0.20.2.2insecure
 arbitrary^0.31.3.2out of date
 arrayvec^0.5.10.7.4out of date
 atomicwrites^0.20.4.3out of date
 base64^0.110.22.0out of date
 bytehash^0.20.3.0out of date
 byteorder^1.2.21.5.0up to date
 cache^0.2.0N/Aup to date
 futures^0.3.10.3.30up to date
 num^0.20.4.2out of date
 owning_ref ⚠️^0.4.00.4.1insecure
 parking_lot^0.6.40.12.2out of date
 quickcheck^0.81.0.3out of date
 rand^0.6.50.8.5out of date
 tempfile^3.0.33.10.1up to date
 wasm-bindgen^0.20.2.92up to date
 web-sys^0.30.3.69up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 tempfile^3.03.10.1up to date

Security Vulnerabilities

appendix: Data race and memory safety issue in `Index`

RUSTSEC-2020-0149

The appendix crate implements a key-value mapping data structure called Index<K, V> that is stored on disk. The crate allows for any type to inhabit the generic K and V type parameters and implements Send and Sync for them unconditionally.

Using a type that is not marked as Send or Sync with Index can allow it to be used across multiple threads leading to data races. Additionally using reference types for the keys or values will lead to the segmentation faults in the crate's code.

owning_ref: Multiple soundness issues in `owning_ref`

RUSTSEC-2022-0040

  • OwningRef::map_with_owner is unsound and may result in a use-after-free.
  • OwningRef::map is unsound and may result in a use-after-free.
  • OwningRefMut::as_owner and OwningRefMut::as_owner_mut are unsound and may result in a use-after-free.
  • The crate violates Rust's aliasing rules, which may cause miscompilations on recent compilers that emit the LLVM noalias attribute.

safer_owning_ref is a replacement crate which fixes these issues. No patched versions of the original crate are available, and the maintainer is unresponsive.