This project contains known security vulnerabilities. Find detailed information at the bottom.
ws_stream_tungstenite(11 total, 3 outdated, 1 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| async-tungstenite | ^0.16 | 0.35.0 | out of date |
| async_io_stream | ^0.3 | 0.3.3 | up to date |
| bitflags | ^1 | 2.13.2 | out of date |
| futures-core | ^0.3 | 0.3.34 | up to date |
| futures-io | ^0.3 | 0.3.34 | up to date |
| futures-sink | ^0.3 | 0.3.34 | up to date |
| futures-util | ^0.3 | 0.3.34 | up to date |
| log | ^0.4 | 0.4.34 | up to date |
| pharos | ^0.5 | 0.5.3 | up to date |
| tokio | ^1 | 1.53.1 | up to date |
| tungstenite ⚠️ | ^0.16 | 0.30.0 | insecure |
(14 total, 5 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| assert_matches | ^1 | 1.5.0 | up to date |
| async-std | ^1 | 1.13.2 | up to date |
| async-tungstenite | ^0.16 | 0.35.0 | out of date |
| async_progress | ^0.2 | 0.2.1 | up to date |
| asynchronous-codec | ^0.6 | 0.7.0 | out of date |
| flexi_logger | ^0.20 | 0.31.10 | out of date |
| futures | ^0.3 | 0.3.34 | up to date |
| futures-test | ^0.3 | 0.3.34 | up to date |
| futures-timer | ^3 | 3.0.4 | up to date |
| futures_ringbuf | ^0.3 | 0.4.0 | out of date |
| pin-utils | ^0.1 | 0.1.0 | up to date |
| tokio | ^1 | 1.53.1 | up to date |
| tokio-util | ^0.6 | 0.7.19 | out of date |
| url | ^2 | 2.5.8 | up to date |
tungstenite: Tungstenite allows remote attackers to cause a denial of serviceThe Tungstenite crate through 0.20.0 for Rust allows remote attackers to cause a denial of service (minutes of CPU consumption) via an excessive length of an HTTP header in a client handshake. The length affects both how many times a parse is attempted (e.g., thousands of times) and the average amount of data for each parse attempt (e.g., millions of bytes).