This project contains known security vulnerabilities. Find detailed information at the bottom.
ziggurat-algorand(30 total, 10 outdated, 1 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0 | 1.0.104 | up to date |
| async-trait | ^0.1 | 0.1.92 | up to date |
| base64 | ^0.13 | 0.23.1 | out of date |
| bytes | ^1 | 1.12.1 | up to date |
| data-encoding | ^2.3 | 2.11.1 | up to date |
| fs_extra | ^1.2 | 1.3.0 | up to date |
| futures-util | ^0.3 | 0.3.34 | up to date |
| home | ^0.5.3 | 0.5.12 | up to date |
| httparse | ^1.8 | 1.10.1 | up to date |
| metrics | ^0.20.0 | 0.24.6 | out of date |
| metrics-util | ^0.14.0 | 0.20.4 | out of date |
| paste | ^1.0 | 1.0.15 | up to date |
| pea2pea | ^0.45 | 0.57.4 | out of date |
| radix_fmt | ^1.0 | 1.0.0 | up to date |
| rand | ^0.8 | 0.10.3 | out of date |
| reqwest | ^0.11 | 0.13.5 | out of date |
| rmp-serde | ^1.0.0 | 1.3.1 | up to date |
| serde_bytes | ^0.11 | 0.11.19 | up to date |
| serde_json | ^1.0 | 1.0.151 | up to date |
| sha2 | ^0.10 | 0.11.0 | out of date |
| tempfile | ^3.3 | 3.27.0 | up to date |
| tokio-tungstenite | ^0.17 | 0.30.0 | out of date |
| tokio-util | ^0.7 | 0.7.19 | up to date |
| toml | ^0.5.9 | 1.1.6+spec-1.1.0 | out of date |
| tungstenite ⚠️ | ^0.17 | 0.30.0 | insecure |
| websocket-codec | ^0.5 | 0.5.2 | up to date |
| serde | ^1 | 1.0.229 | up to date |
| tokio | ^1 | 1.53.1 | up to date |
| tracing | ^0.1 | 0.1.44 | up to date |
| tracing-subscriber | ^0.3 | 0.3.23 | 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).