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 cloud-storage

Dependencies

(17 total, 5 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.1.480.1.83up to date
 base64^0.130.22.1out of date
 bytes^1.01.8.0up to date
 chrono ⚠️^0.40.4.38maybe insecure
 dotenv^0.150.15.0up to date
 futures-util^0.30.3.31up to date
 hex^0.40.4.3up to date
 jsonwebtoken^79.3.0out of date
 lazy_static^11.5.0up to date
 openssl ⚠️^0.100.10.68maybe insecure
 pem^0.83.0.4out of date
 percent-encoding^22.3.1up to date
 reqwest^0.110.12.8out of date
 ring^0.160.17.8out of date
 serde^11.0.213up to date
 serde_json^11.0.132up to date
 tokio ⚠️^1.01.41.0maybe insecure

Dev dependencies

(1 total, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️^1.01.41.0maybe insecure

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);

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.