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, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.411.0.81up to date
 async-trait^0.10.1.79up to date
 bitflags^1.2.12.5.0out of date
 bytes^1.0.11.6.0up to date
 ipnet^2.3.12.9.0up to date
 lazy_static^1.41.4.0up to date
 libc^0.2.80.2.153up to date
 log^0.4.140.4.21up to date
 nix^0.80.28.0out of date
 rand^0.8.40.8.5up to date
 thiserror^1.0.251.0.58up to date
 tokio ⚠️^1.01.36.0maybe insecure
 winapi^0.2.80.3.9out of date

Dev dependencies

(3 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 chrono ⚠️^0.4.190.4.37maybe insecure
 env_logger^0.8.30.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);