Question 1

Is there a bug in tonic 0.12.2?

Accepted Answer

Remotely exploitable Denial of Service in Tonic ## 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](https://github.com/hyperium/tonic/issues/1897)

## Patches

Upgrading to tonic `0.12.3` and above contains the fix.

## Workarounds

A custom accept loop is a possible workaround. Fixed in tonic 0.12.3.

Question 2

Is there a bug in tonic 0.12.2?

Accepted Answer

Tonic has remotely exploitable denial of service vulnerability ### 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](https://github.com/hyperium/tonic/issues/1897)

### Patches

Upgrading to tonic `0.12.3` and above contains the fix.

### Workarounds

A custom accept loop is a possible workaround. Fixed in tonic 0.12.3.

Severity	Affected	Fixed in	Title	Status	Source
medium	0.12.2	0.12.3	Remotely exploitable Denial of Service in Tonic ## 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](https://github.com/hyperium/tonic/issues/1897) ## Patches Upgrading to tonic `0.12.3` and above contains the fix. ## Workarounds A custom accept loop is a possible workaround.	fixed	osv:RUSTSEC-2024-0376
medium	0.12.2	0.12.3	Tonic has remotely exploitable denial of service vulnerability ### 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](https://github.com/hyperium/tonic/issues/1897) ### Patches Upgrading to tonic `0.12.3` and above contains the fix. ### Workarounds A custom accept loop is a possible workaround.	fixed	osv:GHSA-4jwc-w2hc-78qv

tonic known bugs