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 turn

Dependencies

(10 total, 6 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 webrtc-util^0.5.40.10.0out of date
 stun^0.4.20.7.0out of date
 tokio ⚠️^1.191.44.1maybe insecure
 async-trait^0.1.560.1.88up to date
 log^0.40.4.26up to date
 base64^0.13.00.22.1out of date
 rand^0.8.50.9.0out of date
 ring ⚠️^0.16.200.17.14out of date
 md-5^0.10.10.10.6up to date
 thiserror^1.02.0.12out of date

Dev dependencies

(6 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio-test^0.4.00.4.4up to date
 env_logger^0.9.00.11.7out of date
 chrono ⚠️^0.4.190.4.40maybe insecure
 hex^0.4.30.4.3up to date
 clap^3.2.64.5.32out of date
 criterion^0.3.50.5.1out of 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);

ring: Some AES functions may panic when overflow checking is enabled.

RUSTSEC-2025-0009

ring::aead::quic::HeaderProtectionKey::new_mask() may panic when overflow checking is enabled. In the QUIC protocol, an attacker can induce this panic by sending a specially-crafted packet. Even unintentionally it is likely to occur in 1 out of every 2**32 packets sent and/or received.

On 64-bit targets operations using ring::aead::{AES_128_GCM, AES_256_GCM} may panic when overflow checking is enabled, when encrypting/decrypting approximately 68,719,476,700 bytes (about 64 gigabytes) of data in a single chunk. Protocols like TLS and SSH are not affected by this because those protocols break large amounts of data into small chunks. Similarly, most applications will not attempt to encrypt/decrypt 64GB of data in one chunk.

Overflow checking is not enabled in release mode by default, but RUSTFLAGS="-C overflow-checks" or overflow-checks = true in the Cargo.toml profile can override this. Overflow checking is usually enabled by default in debug mode.