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 octocrab

Dependencies

(33 total, 1 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 arc-swap^1.3.01.7.1up to date
 async-trait^0.1.500.1.80up to date
 base64^0.22.00.22.1up to date
 bytes^1.0.11.6.0up to date
 cfg-if^1.0.01.0.0up to date
 chrono ⚠️^0.4.190.4.38maybe insecure
 either^1.8.01.12.0up to date
 futures^0.3.150.3.30up to date
 futures-core^0.3.150.3.30up to date
 futures-util^0.3.150.3.30up to date
 http^1.0.01.1.0up to date
 http-body^1.0.01.0.0up to date
 http-body-util^0.1.00.1.1up to date
 hyper^1.1.01.3.1up to date
 hyper-rustls^0.26.00.27.1out of date
 hyper-timeout^0.5.10.5.1up to date
 hyper-tls^0.6.00.6.0up to date
 hyper-util^0.1.30.1.3up to date
 jsonwebtoken^99.3.0up to date
 once_cell^1.7.21.19.0up to date
 percent-encoding^2.2.02.3.1up to date
 pin-project^1.0.121.1.5up to date
 secrecy^0.8.00.8.0up to date
 serde^1.0.1261.0.202up to date
 serde_json^1.0.641.0.117up to date
 serde_path_to_error^0.1.40.1.16up to date
 serde_urlencoded^0.7.10.7.1up to date
 snafu^0.80.8.2up to date
 tokio ⚠️^1.17.01.37.0maybe insecure
 tower^0.4.130.4.13up to date
 tower-http^0.5.10.5.2up to date
 tracing^0.1.370.1.40up to date
 url^2.2.22.5.0up to date

Dev dependencies

(7 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 base64^0.22.00.22.1up to date
 crypto_box^0.8.20.9.1out of date
 graphql_client^0.14.00.14.0up to date
 pretty_assertions^1.4.01.4.0up to date
 tokio ⚠️^1.17.01.37.0maybe insecure
 tokio-test^0.4.20.4.4up to date
 wiremock^0.6.00.6.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);