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 fireblocks-sdk

Dependencies

(24 total, 2 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.97up to date
 async-trait^0.10.1.87up to date
 bon^33.4.0up to date
 bytes^11.10.1up to date
 chrono ⚠️^0.40.4.40maybe insecure
 futures^0.30.3.31up to date
 http^11.3.1up to date
 jsonwebtoken^99.3.1up to date
 rand^0.80.9.0out of date
 reqwest-middleware^0.40.4.1up to date
 reqwest-retry^0.70.7.0up to date
 reqwest-tracing^0.50.5.6up to date
 reqwest^0.120.12.14up to date
 serde_json^1.01.0.140up to date
 serde_repr^0.10.1.20up to date
 serde^1.01.0.219up to date
 serde_with^3.83.12.0up to date
 sha2^0.100.10.8up to date
 thiserror^12.0.12out of date
 tokio-util^0.70.7.14up to date
 tokio ⚠️^11.44.1maybe insecure
 tracing^0.10.1.41up to date
 url^2.52.5.4up to date
 uuid^1.81.15.1up to date

Dev dependencies

(6 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 tracing-subscriber^0.30.3.19up to date
 tokio ⚠️^11.44.1maybe insecure
 lazy_static^1.4.01.5.0up to date
 dotenvy^0.150.15.7up to date
 tokio-stream^0.10.1.17up to date
 rstest^0.24.00.25.0out of 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);