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 webrtc-dtls

Dependencies

(32 total, 19 outdated, 4 possibly insecure)

CrateRequiredLatestStatus
 webrtc-util^0.5.40.9.0out of date
 byteorder^11.5.0up to date
 rand_core^0.6.30.6.4up to date
 elliptic-curve^0.12.10.13.8out of date
 hkdf~0.12.10.12.4up to date
 curve25519-dalek ⚠️^3.24.1.3out of date
 p256^0.11.10.13.2out of date
 rand^0.8.50.8.5up to date
 hmac^0.10.10.12.1out of date
 sha-1^0.9.10.10.1out of date
 sha2^0.9.10.10.8out of date
 aes^0.6.00.8.4out of date
 block-modes^0.7.00.9.1out of date
 aes-gcm^0.8.00.10.3out of date
 ccm^0.3.00.5.0out of date
 tokio ⚠️^1.191.40.0maybe insecure
 async-trait^0.1.560.1.83up to date
 x25519-dalek^2.0.0-pre.12.0.1up to date
 signature^1.2.22.2.0out of date
 oid-registry^0.6.00.7.1out of date
 x509-parser^0.13.20.16.0out of date
 der-parser^8.19.0.0out of date
 rcgen^0.9.20.13.1out of date
 ring^0.16.190.17.8out of date
 webpki ⚠️^0.21.40.22.4out of date
 rustls ⚠️^0.19.00.23.14out of date
 bincode^1.31.3.3up to date
 serde^1.01.0.210up to date
 serde_derive^1.01.0.210up to date
 subtle^2.42.6.1up to date
 log^0.40.4.22up to date
 thiserror^1.01.0.64up to date

Dev dependencies

(4 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio-test^0.4.00.4.4up to date
 env_logger^0.9.00.11.5out of date
 chrono ⚠️^0.4.190.4.38maybe insecure
 clap^3.2.64.5.20out of date

Crate hub

Dependencies

(8 total, 5 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 webrtc-util^0.5.40.9.0out of date
 tokio ⚠️^1.191.40.0maybe insecure
 x509-parser^0.13.00.16.0out of date
 rcgen^0.9.20.13.1out of date
 ring^0.16.190.17.8out of date
 rustls ⚠️^0.19.00.23.14out of date
 log^0.40.4.22up to date
 thiserror^1.01.0.64up 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);

webpki: webpki: CPU denial of service in certificate path building

RUSTSEC-2023-0052

When 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 input

RUSTSEC-2024-0336

If 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`

RUSTSEC-2024-0344

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:

https://github.com/Fraunhofer-AISEC/DATA