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

Dependencies

(21 total, 3 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.10.1.83up to date
 bytes^11.9.0up to date
 chrono ⚠️^0.40.4.39maybe insecure
 futures^0.30.3.31up to date
 hyper^11.5.2up to date
 jsonwebtoken^99.3.0up to date
 once_cell^1.191.20.2up to date
 prost^0.130.13.4up to date
 prost-types^0.130.13.4up to date
 reqwest>=0.12.70.12.9up to date
 secret-vault-value^0.30.3.9up to date
 serde^11.0.216up to date
 serde_json^11.0.133up to date
 serde_with^33.11.0up to date
 tokio ⚠️^11.42.0maybe insecure
 tonic ⚠️^0.120.12.3maybe insecure
 tower^0.50.5.2up to date
 tower-layer^0.30.3.3up to date
 tower-util^0.30.3.1up to date
 tracing^0.10.1.41up to date
 url^2.52.5.4up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 cargo-audit^0.210.21.0up 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);

tonic: Remotely exploitable Denial of Service in Tonic

RUSTSEC-2024-0376

Impact

When using tonic::transport::Server there is a remote DoS attack that can cause the server to exit cleanly on accepting a tcp/tls stream. This can be triggered via causing the accept call to error out with errors there were not covered correctly causing the accept loop to exit.

More information can be found here

Patches

Upgrading to tonic 0.12.3 and above contains the fix.

Workarounds

A custom accept loop is a possible workaround.