This is an automated email from the ASF dual-hosted git repository.

viirya pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/spark-connect-gateway.git


The following commit(s) were added to refs/heads/main by this push:
     new 2de43b9  [SPARK-60371] Update quinn-proto and rustls in Cargo.lock to 
pick up recent RustSec advisories
2de43b9 is described below

commit 2de43b973fa5ce6783d55617b43ea2a5675a8e11
Author: Liang-Chi Hsieh <[email protected]>
AuthorDate: Wed Oct 21 23:04:30 2026 -0700

    [SPARK-60371] Update quinn-proto and rustls in Cargo.lock to pick up recent 
RustSec advisories
    
    ### What changes were proposed in this pull request?
    
    Update two crates in `Cargo.lock` to pick up fixes for nine RustSec 
advisories.
    Lockfile-only; no `Cargo.toml` change is needed.
    
    ```
    cargo update -p quinn-proto --precise 0.11.19
    cargo update -p rustls --precise 0.23.46
    ```
    
    The resolved set is **431 crates before and after**; `quinn-proto`
    (0.11.16 -> 0.11.19) and `rustls` (0.23.45 -> 0.23.46) are the only two 
whose
    version changes.
    
    ### Why are the changes needed?
    
    `cargo audit` against `main` (af4f080) reports these, all with fixed 
releases.
    
    **`rustls` 0.23.45 -> 0.23.46.** These apply: the gateway uses rustls as a 
TLS
    client (`kube-client` for the K8s API, `reqwest` for OIDC JWKS, tonic /
    `opentelemetry-otlp`).
    
    | Advisory | Issue |
    |---|---|
    | RUSTSEC-2026-0346 | `Debug` impls for client session values expose TLS 
secrets |
    | RUSTSEC-2026-0347 | buffered application data sent to outer server after 
ECH rejection |
    | RUSTSEC-2026-0348 | brotli certificate decompression can allocate up to 1 
GiB before authentication |
    | RUSTSEC-2026-0349 | unauthenticated ServerHello can downgrade later 
connections to classical key exchange |
    
    **`quinn-proto` 0.11.16 -> 0.11.19.** The gateway is not exposed to these.
    `quinn` is enabled only by reqwest's `http3` feature, which the workspace 
does
    not turn on (`reqwest` is built with `rustls-tls` and `json`), so 
`quinn-proto`
    appears in `Cargo.lock` but is never compiled. `cargo audit` reads the 
lockfile
    rather than the build graph, so it still reports them, and updating is
    preferable to ignoring advisories that have a fix.
    
    | Advisory | Issue |
    |---|---|
    | RUSTSEC-2026-0338 | zero-length STREAM frames can panic during unordered 
reads |
    | RUSTSEC-2026-0339 | unbounded growth of pending connection ID retirements 
|
    | RUSTSEC-2026-0340 | peer minimum ACK delay can panic with ACK_FREQUENCY |
    | RUSTSEC-2026-0341 | stream reassembly memory-exhaustion guard can be 
bypassed |
    | RUSTSEC-2026-0342 | zero-length DATAGRAM frames bypass the receive buffer 
limit |
    
    This is also a step toward SPARK-60370 (running `cargo audit` in CI).
    
    **Not covered here:** RUSTSEC-2026-0381 (`webpki-roots`) and
    RUSTSEC-2026-0382 (`rustls-webpki`) were published after this change was
    prepared and will be handled separately.
    
    ### Does this PR introduce _any_ user-facing change?
    
    No. No configuration or API change. The behavioural effect is confined to 
the
    outbound TLS client fixes listed above.
    
    ### How was this patch tested?
    
    On the pinned 1.99.0 toolchain:
    
    - `cargo audit` no longer reports any `quinn-proto` or `rustls` advisory.
    - `cargo clippy --workspace --all-targets -- -D warnings` -- clean.
    - `cargo fmt --all -- --check` -- clean.
    - `cargo test --workspace` -- 204 passed, 0 failed, 10 ignored, matching the
      baseline on `main`. `rustls` is compiled into the gateway, so this 
exercises
      the new version.
    - The build produces no `quinn` artifact, confirming `quinn-proto` is not
      compiled.
    - The lockfile claim was checked by comparing the full resolved package set
      (name + version for all 431 entries) against `main`, not by reading the 
diff.
    
    ### Was this patch authored or co-authored using generative AI tooling?
    
    Yes, co-authored with Claude Code.
    
    Closes #51 from viirya/dep-06-quinn-rustls.
    
    Authored-by: Liang-Chi Hsieh <[email protected]>
    Signed-off-by: Liang-Chi Hsieh <[email protected]>
---
 Cargo.lock | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/Cargo.lock b/Cargo.lock
index 86f2b12..433fd64 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -872,7 +872,7 @@ source = 
"registry+https://github.com/rust-lang/crates.io-index";
 checksum = "39cab71617ae0d63f51a36d69f866391735b51691dbda63cf6f96d042b63efeb"
 dependencies = [
  "libc",
- "windows-sys 0.52.0",
+ "windows-sys 0.61.2",
 ]
 
 [[package]]
@@ -2559,9 +2559,9 @@ dependencies = [
 
 [[package]]
 name = "quinn-proto"
-version = "0.11.16"
+version = "0.11.19"
 source = "registry+https://github.com/rust-lang/crates.io-index";
-checksum = "2f4bfc015262b9df63c8845072ce59068853ff5872180c2ce2f13038b970e560"
+checksum = "0e750cca55fe4f0439a15d0bb529da9651e79993e8e72c61a899a36d462befbe"
 dependencies = [
  "bytes",
  "getrandom 0.4.3",
@@ -2590,7 +2590,7 @@ dependencies = [
  "once_cell",
  "socket2",
  "tracing",
- "windows-sys 0.52.0",
+ "windows-sys 0.61.2",
 ]
 
 [[package]]
@@ -2891,14 +2891,14 @@ dependencies = [
  "errno",
  "libc",
  "linux-raw-sys",
- "windows-sys 0.52.0",
+ "windows-sys 0.61.2",
 ]
 
 [[package]]
 name = "rustls"
-version = "0.23.45"
+version = "0.23.46"
 source = "registry+https://github.com/rust-lang/crates.io-index";
-checksum = "0d41d731c7d2f962d1ccc364cec258de3c0e93b38c2fb3ba97ac74513048d634"
+checksum = "48e13bd8c0e9365c43cfa5c9e8f9ad49d3c8444926c9aac819e0e4dc503c8fdf"
 dependencies = [
  "log",
  "once_cell",
@@ -3566,10 +3566,10 @@ source = 
"registry+https://github.com/rust-lang/crates.io-index";
 checksum = "32497e9a4c7b38532efcdebeef879707aa9f794296a4f0244f6f69e9bc8574bd"
 dependencies = [
  "fastrand",
- "getrandom 0.4.3",
+ "getrandom 0.3.4",
  "once_cell",
  "rustix",
- "windows-sys 0.52.0",
+ "windows-sys 0.61.2",
 ]
 
 [[package]]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to