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

(31 total, 20 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 aes^0.6.00.8.4out of date
 aes-gcm^0.8.00.10.3out of date
 anyhow^1.0.411.0.81up to date
 async-trait^0.10.1.79up to date
 bincode^1.3.11.3.3up to date
 block-modes^0.7.00.9.1out of date
 byteorder^1.3.21.5.0up to date
 ccm^0.3.00.5.0out of date
 der-parser^5.09.0.0out of date
 elliptic-curve^0.8.40.13.8out of date
 hmac^0.10.10.12.1out of date
 lazy_static^1.3.01.4.0up to date
 log^0.40.4.21up to date
 oid-registry^0.1.10.7.0out of date
 p256^0.7.10.13.2out of date
 rand^0.8.00.8.5up to date
 rand_core^0.50.6.4out of date
 rcgen^0.8.90.13.0out of date
 ring^0.16.190.17.8out of date
 rustls^0.19.00.23.4out of date
 serde^1.01.0.197up to date
 serde_derive^1.01.0.197up to date
 sha-1^0.9.10.10.1out of date
 sha2^0.9.10.10.8out of date
 signature^1.2.22.2.0out of date
 thiserror^1.0.251.0.58up to date
 tokio ⚠️^1.01.36.0maybe insecure
 webrtc-util^0.4.10.8.1out of date
 webpki ⚠️^0.21.40.22.4out of date
 x25519-dalek^1.1.02.0.1out of date
 x509-parser^0.90.16.0out of date

Dev dependencies

(4 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 chrono ⚠️^0.4.190.4.37maybe insecure
 clap^24.5.4out of date
 env_logger^0.80.11.3out of date
 tokio-test^0.40.4.4up 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.