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.
webrtc-data(7 total, 4 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| webrtc-util | ^0.5.4 | 0.9.0 | out of date |
| webrtc-sctp | ^0.5.0 | 0.10.0 | out of date |
| tokio ⚠️ | ^1.19 | 1.41.1 | maybe insecure |
| bytes | ^1 | 1.8.0 | up to date |
| derive_builder | ^0.11.2 | 0.20.2 | out of date |
| log | ^0.4 | 0.4.22 | up to date |
| thiserror | ^1.0 | 2.0.3 | out of date |
(3 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| tokio-test | ^0.4.0 | 0.4.4 | up to date |
| env_logger | ^0.9.0 | 0.11.5 | out of date |
| chrono ⚠️ | ^0.4.19 | 0.4.38 | maybe insecure |
chrono: Potential segfault in `localtime_r` invocationsUnix-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.
No workarounds are known.
tokio: reject_remote_clients Configuration corruptionOn 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.
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);