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.
bitreq(12 total, 5 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| base64 | ^0.22 | 0.22.1 | up to date |
| log | ^0.4.0 | 0.4.29 | up to date |
| punycode | ^0.4.1 | 0.4.1 | up to date |
| rustls ⚠️ | ^0.21.1 | 0.23.37 | out of date |
| rustls-native-certs | ^0.6.1 | 0.8.3 | out of date |
| rustls-webpki ⚠️ | ^0.101.0 | 0.103.10 | out of date |
| serde | ^1.0.101 | 1.0.228 | up to date |
| serde_json | ^1.0.0 | 1.0.149 | up to date |
| tokio ⚠️ | ^1.0 | 1.50.0 | maybe insecure |
| tokio-rustls | ^0.24 | 0.26.4 | out of date |
| urlencoding | ^2.1.0 | 2.1.3 | up to date |
| webpki-roots | ^0.25.2 | 1.0.6 | out of date |
(2 total, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| chrono ⚠️ | ^0.4.0 | 0.4.44 | maybe insecure |
| tiny_http | ^0.12 | 0.12.0 | up to date |
chrono: Potential segfault in `localtime_r` invocationsUnix-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.
No workarounds are known.
tokio: reject_remote_clients Configuration corruptionOn 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.
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);
rustls-webpki: rustls-webpki: CPU denial of service in certificate path buildingWhen this crate is given a pathological certificate chain to validate, it will spend CPU time exponential with the number of candidate certificates at each step of path building.
Both TLS clients and TLS servers that accept client certificate are affected.
We now give each path building operation a budget of 100 signature verifications.
The original webpki crate is also affected.
This was previously reported in the original crate https://github.com/briansmith/webpki/issues/69 and re-reported to us recently by Luke Malinowski.
rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network inputIf a close_notify alert is received during a handshake, complete_io
does not terminate.
Callers which do not call complete_io are not affected.
rustls-tokio and rustls-ffi do not call complete_io
and are not affected.
rustls::Stream and rustls::StreamOwned types use
complete_io and are affected.