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 mentedb-embedding

Dependencies

(15 total, 5 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 candle-core^0.110.11.0up to date
 candle-nn^0.110.11.0up to date
 candle-transformers^0.110.11.0up to date
 chrono ⚠️^0.40.4.45maybe insecure
 hf-hub^0.41.0.0out of date
 hmac^0.120.13.0out of date
 mentedb-core^0.12.60.14.0out of date
 serde^11.0.228up to date
 serde_json^11.0.150up to date
 sha2^0.100.11.0out of date
 thiserror^22.0.18up to date
 tokenizers^0.210.23.1out of date
 tokio ⚠️^11.52.3maybe insecure
 tracing^0.10.1.44up to date
 ureq^33.3.0up to date

Dev dependencies

(3 total, 1 possibly insecure)

CrateRequiredLatestStatus
 tempfile^33.27.0up to date
 tokio ⚠️^11.52.3maybe insecure
 uuid^11.23.5up to date

Security Vulnerabilities

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

tokio: reject_remote_clients Configuration corruption

RUSTSEC-2023-0001

On Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.

This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.

The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.

Workarounds

Ensure that pipe_mode is set first after initializing a ServerOptions. For example:

let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);