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

(11 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.411.0.81up to date
 async-trait^0.10.1.79up to date
 base64^0.13.00.22.0out of date
 log^0.40.4.21up to date
 md-5^0.9.10.10.6out of date
 rand^0.8.20.8.5up to date
 ring^0.16.190.17.8out of date
 stun^0.3.10.5.1out of date
 thiserror^1.0.251.0.58up to date
 tokio ⚠️^1.01.37.0maybe insecure
 webrtc-util^0.4.10.8.1out of date

Dev dependencies

(5 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
 hex^0.4.20.4.3up to 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);