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.
tonic-web-wasm-client(17 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| base64 | ^0.22 | 0.22.1 | up to date |
| byteorder | ^1 | 1.5.0 | up to date |
| bytes | ^1 | 1.10.1 | up to date |
| futures-util | ^0.3 | 0.3.31 | up to date |
| http | ^1 | 1.3.1 | up to date |
| http-body | ^1 | 1.0.1 | up to date |
| http-body-util | ^0.1 | 0.1.3 | up to date |
| httparse | ^1 | 1.10.1 | up to date |
| js-sys | ^0.3 | 0.3.77 | up to date |
| pin-project | ^1 | 1.1.10 | up to date |
| thiserror | ^1 | 2.0.12 | out of date |
| tonic ⚠️ | ^0.12 | 0.12.3 | maybe insecure |
| tower-service | ^0.3 | 0.3.3 | up to date |
| wasm-bindgen | ^0.2 | 0.2.100 | up to date |
| wasm-bindgen-futures | ^0.4 | 0.4.50 | up to date |
| wasm-streams | ^0.4 | 0.4.2 | up to date |
| web-sys | ^0.3 | 0.3.77 | up to date |
tonic: Remotely exploitable Denial of Service in TonicWhen using tonic::transport::Server there is a remote DoS attack that can cause the server to exit cleanly on accepting a tcp/tls stream. This can be triggered via causing the accept call to error out with errors there were not covered correctly causing the accept loop to exit.
More information can be found here
Upgrading to tonic 0.12.3 and above contains the fix.
A custom accept loop is a possible workaround.