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.
libp2p-webrtc(17 total, 7 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0.52 | 1.0.86 | up to date |
| async-datachannel | ^0.2.2 | 0.4.0 | out of date |
| async-datachannel-wasm | ^0.1.2 | 0.2.1 | out of date |
| async-stream | ^0.3.2 | 0.3.5 | up to date |
| async-tungstenite | ^0.16.1 | 0.25.1 | out of date |
| futures-timer | ^3.0.2 | 3.0.3 | up to date |
| http | ^0.2.6 | 1.1.0 | out of date |
| libp2p ⚠️ | ^0.41.1 | 0.53.2 | out of date |
| log | ^0.4.14 | 0.4.21 | up to date |
| parking_lot | ^0.11.2 | 0.12.2 | out of date |
| pin-project | ^1.0.10 | 1.1.5 | up to date |
| send_wrapper | ^0.5.0 | 0.6.0 | out of date |
| serde | ^1.0.133 | 1.0.202 | up to date |
| serde_json | ^1.0.74 | 1.0.117 | up to date |
| streamunordered | ^0.5.2 | 0.5.3 | up to date |
| thiserror | ^1.0.30 | 1.0.61 | up to date |
| ws_stream_wasm | ^0.7.3 | 0.7.4 | up to date |
(6 total, 2 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| console_log | ^0.2.0 | 1.0.0 | out of date |
| libp2p ⚠️ | ^0.41.1 | 0.53.2 | out of date |
| tokio ⚠️ | ^1.15.0 | 1.37.0 | maybe insecure |
| tracing-subscriber | ^0.3.5 | 0.3.18 | up to date |
| wasm-bindgen-futures | ^0.4.28 | 0.4.42 | up to date |
| wasm-bindgen-test | ^0.3.28 | 0.3.42 | up to date |
libp2p: libp2p Lack of resource management DoSlibp2p allows a potential attacker to cause victim p2p node to run out of memory
The out of memory failure can cause crashes where libp2p is intended to be used within large scale networks leading to potential Denial of Service (DoS) vector
Users should upgrade or reference the DoS mitigation strategies.
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);