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

fix(deps): update rust crate tonic to 0.12 [security] - autoclosed #341

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 2, 2024

This PR contains the following updates:

Package Type Update Change
tonic dependencies minor 0.11 -> 0.12

GitHub Vulnerability Alerts

CVE-2024-47609

Impact

note: this only affects v0.12.0 - v0.12.2

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.


Release Notes

hyperium/tonic (tonic)

v0.12.3

Compare Source

Features
  • server: Added support for grpc max_connection_age (#​1865)
  • build: Add #[deprecated] to deprecated client methods (#​1879)
  • build: plumb skip_debug through prost Builder and add test (#​1900)
Bug Fixes
  • build: Revert "fix tonic-build cargo build script outputs (#​1821)" which accidentally increases MSRV (#​1898)
  • server: ignore more error kinds in incoming socket stream (#​1885)
  • transport: do not shutdown server on broken connections (#​1948)

v0.12.2

Compare Source

Features
  • Move TimeoutExpired out of transport (#​1826)
  • Move ConnectError type from transport (#​1828)
  • channel: allow setting max_header_list_size (#​1835)
  • router: Add RoutesBuilder constructor (#​1855)
  • tls: Rename tls-roots feature with tls-native-roots (#​1860)
  • router: Rename Routes::into_router with into_axum_router (#​1862)
  • router: Implement from axum::Router for Routes (#​1863)
  • channel: Re-enable TLS based on Cargo features in generated clients (#​1866)
  • server: allow setting max_header_list_size (#​1870)
  • build: Expose formatted service name (#​1684)
  • reflection: add back support for v1alpha reflection protocol (#​1888)
Bug Fixes
  • router: Add missing unimplemented fallback to RoutesBuilder (#​1864)
  • server: Prevent server from exiting on ECONNABORTED (#​1874)
  • web: fix panic in trailer parsing on multiple trailers (#​1880)
  • web: fix empty trailer parsing causing infinite parser loop (#​1883)

v0.12.1

Compare Source

Bug Fixes
  • Reduce tokio-stream feature (#​1795)

v0.12.0

Compare Source

This breaking release updates tonic to the hyper 1.0 ecosystem and also updates
to prost v0.13.0.

Features
Bug Fixes
BREAKING CHANGES
  • tonic and crates updated to hyper 1.0 (#​1670)
  • tonic and crates updated to prost 0.13 (#​1779)
  • tonic_reflection::server is updated to use the generated
    tonic_reflection::pb::v1 code.
  • Make compression encoding configuration more malleable (#​1757)
  • Removed implicit configuration of client TLS roots setup (#​1731)

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title fix(deps): update rust crate tonic to 0.12 [security] fix(deps): update rust crate tonic to 0.12 [security] - autoclosed Oct 2, 2024
@renovate renovate bot closed this Oct 2, 2024
@renovate renovate bot deleted the renovate/crate-tonic-vulnerability branch October 2, 2024 18:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants