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.
webrtc-dtls(32 total, 19 outdated, 4 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| aes | ^0.6.0 | 0.8.4 | out of date |
| aes-gcm | ^0.8.0 | 0.10.3 | out of date |
| async-trait | ^0.1.56 | 0.1.83 | up to date |
| bincode | ^1.3 | 1.3.3 | up to date |
| block-modes | ^0.7.0 | 0.9.1 | out of date |
| byteorder | ^1 | 1.5.0 | up to date |
| ccm | ^0.3.0 | 0.5.0 | out of date |
| curve25519-dalek ⚠️ | ^3.2 | 4.1.3 | out of date |
| der-parser | ^8.1 | 9.0.0 | out of date |
| elliptic-curve | ^0.12.1 | 0.13.8 | out of date |
| hkdf | ~0.12.1 | 0.12.4 | up to date |
| hmac | ^0.10.1 | 0.12.1 | out of date |
| log | ^0.4 | 0.4.22 | up to date |
| oid-registry | ^0.6.0 | 0.7.1 | out of date |
| p256 | ^0.11.1 | 0.13.2 | out of date |
| rand | ^0.8.5 | 0.8.5 | up to date |
| rand_core | ^0.6.3 | 0.6.4 | up to date |
| rcgen | ^0.9.2 | 0.13.1 | out of date |
| ring | ^0.16.19 | 0.17.8 | out of date |
| rustls ⚠️ | ^0.19.0 | 0.23.16 | out of date |
| serde | ^1.0 | 1.0.214 | up to date |
| serde_derive | ^1.0 | 1.0.214 | up to date |
| sha-1 | ^0.9.1 | 0.10.1 | out of date |
| sha2 | ^0.9.1 | 0.10.8 | out of date |
| signature | ^1.2.2 | 2.2.0 | out of date |
| subtle | ^2.4 | 2.6.1 | up to date |
| thiserror | ^1.0 | 1.0.65 | up to date |
| tokio ⚠️ | ^1.19 | 1.41.0 | maybe insecure |
| webrtc-util | ^0.5.4 | 0.9.0 | out of date |
| webpki ⚠️ | ^0.21.4 | 0.22.4 | out of date |
| x25519-dalek | ^2.0.0-pre.1 | 2.0.1 | up to date |
| x509-parser | ^0.13.2 | 0.16.0 | out of date |
(4 total, 2 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| chrono ⚠️ | ^0.4.19 | 0.4.38 | maybe insecure |
| clap | ^3.2.6 | 4.5.20 | out of date |
| env_logger | ^0.9.0 | 0.11.5 | out of date |
| tokio-test | ^0.4.0 | 0.4.4 | 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);
webpki: 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.
This was previously reported in https://github.com/briansmith/webpki/issues/69 and re-reported recently by Luke Malinowski.
webpki 0.22.1 included a partial fix and webpki 0.22.2 added further fixes.
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.
curve25519-dalek: Timing variability in `curve25519-dalek`'s `Scalar29::sub`/`Scalar52::sub`Timing variability of any kind is problematic when working with potentially secret values such as
elliptic curve scalars, and such issues can potentially leak private keys and other secrets. Such a
problem was recently discovered in curve25519-dalek.
The Scalar29::sub (32-bit) and Scalar52::sub (64-bit) functions contained usage of a mask value
inside a loop where LLVM saw an opportunity to insert a branch instruction (jns on x86) to
conditionally bypass this code section when the mask value is set to zero as can be seen in godbolt:
A similar problem was recently discovered in the Kyber reference implementation:
https://groups.google.com/a/list.nist.gov/g/pqc-forum/c/hqbtIGFKIpU/m/cnE3pbueBgAJ
As discussed on that thread, one portable solution, which is also used in this PR, is to introduce a volatile read as an optimization barrier, which prevents the compiler from optimizing it away.
The fix can be validated in godbolt here:
The problem was discovered and the solution independently verified by Alexander Wagner [email protected] and Lea Themint [email protected] using their DATA tool: