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-util

Dependencies

(13 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.1.560.1.83up to date
 bitflags^1.32.6.0out of date
 bytes^11.8.0up to date
 ipnet^2.52.10.1up to date
 lazy_static^1.41.5.0up to date
 libc^0.2.1260.2.161up to date
 log^0.4.160.4.22up to date
 nix^0.24.10.29.0out of date
 parking_lot^0.12.10.12.3up to date
 rand^0.8.50.8.5up to date
 thiserror~1.0.21.0.65up to date
 tokio ⚠️^1.191.41.0maybe insecure
 winapi^0.3.90.3.9up to date

Dev dependencies

(5 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-global-executor>=2.0.0, <=2.2.02.4.1out of date
 chrono ⚠️^0.4.190.4.38maybe insecure
 criterion^0.3.50.5.1out of date
 env_logger^0.9.00.11.5out of date
 tokio-test^0.4.00.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);