Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RUSTSEC-2024-0376: Remotely exploitable Denial of Service in Tonic #18789

Open
github-actions bot opened this issue Oct 3, 2024 · 1 comment
Open

RUSTSEC-2024-0376: Remotely exploitable Denial of Service in Tonic #18789

github-actions bot opened this issue Oct 3, 2024 · 1 comment

Comments

@github-actions
Copy link
Contributor

github-actions bot commented Oct 3, 2024

Remotely exploitable Denial of Service in Tonic

Details
Package tonic
Version 0.12.2
URL GHSA-4jwc-w2hc-78qv
Date 2024-10-01
Patched versions >=0.12.3
Unaffected versions <=0.11.0

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.

See advisory page for additional details.

Copy link
Contributor Author

github-actions bot commented Dec 2, 2024

This issue has been open for 60 days with no activity.

If you think it is still relevant today, and needs to be done in the near future, you can comment to update the status, or just manually remove the no-issue-activity label.

You can also confidently close this issue as not planned to keep our backlog clean.
Don't worry if you think the issue is still valuable to continue in the future.
It's searchable and can be reopened when it's time. 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants