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 orientdb-client

Dependencies

(11 total, 3 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 chrono ⚠️^0.4.70.4.38maybe insecure
 byteorder^1.3.21.5.0up to date
 r2d2^0.8.50.8.10up to date
 nom^6.17.1.3out of date
 thiserror^1.0.131.0.59up to date
 async-std^1.91.12.0up to date
 async-trait^0.1.100.1.80up to date
 futures^0.30.3.30up to date
 mobc^0.70.8.4out of date
 tokio ⚠️^11.37.0maybe insecure
 uuid^0.81.8.0out of date

Dev dependencies

(2 total, 2 outdated)

CrateRequiredLatestStatus
 dotenv^0.14.10.15.0out of date
 uuid^0.81.8.0out of date

Crate orientdb-macro

Dependencies

(3 total, 1 outdated)

CrateRequiredLatestStatus
 proc-macro2^1.0.91.0.81up to date
 syn^1.0.162.0.60out of date
 quote^1.0.21.0.36up 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);