Vulnerability MediumRUSTSEC-2024-0376 · tonic
RUSTSEC-2024-0376: Remotely exploitable Denial of Service in Tonic
Short answerA security vulnerability in the tonic crate: Remotely exploitable Denial of Service in Tonic. GitHub rates it Medium. Fixed in 0.12.3: update to a fixed version.
| Crate | tonic |
|---|---|
| Type | Vulnerability (denial-of-service) |
| Affected versions | From 0.12.2 before 0.12.3. |
| Fixed in | 0.12.3 |
| Severity | Medium (GitHub rating) |
| Published | 2024-10-01 |
| Last changed | 2026-10-12 |
| Also known as | CVE-2024-47609, GHSA-4jwc-w2hc-78qv |
What to do
- See which version you have:
cargo tree -i tonic(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p tonic. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for exampletonic = "0.12.3") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
Impact
When 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
Patches
Upgrading to tonic 0.12.3 and above contains the fix.
Workarounds
A custom accept loop is a possible workaround.
References
- Package: crates.io/crates/tonic
- Advisory: rustsec.org/advisories/RUSTSEC-2024-0376.html
- Report: github.com/hyperium/tonic/issues/1897
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Same cratetonic: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?