GHSA-4jwc-w2hc-78qv
MEDIUMGHSA-4jwc-w2hc-78qv is a medium-severity (CVSS 5.3) CWE-755 vulnerability in tonic. O3 Security confirms whether GHSA-4jwc-w2hc-78qv is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Tonic has remotely exploitable denial of service vulnerability
Blast Radius
tonicReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | tonic | ≥ 0.12.2&&< 0.12.3 | 0.12.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tonic. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update tonic to 0.12.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4jwc-w2hc-78qv is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-4jwc-w2hc-78qv is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-4jwc-w2hc-78qv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-4jwc-w2hc-78qv in your dependencies?
O3 detects GHSA-4jwc-w2hc-78qv across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.