Skip to content

deps: bump aws-lc-sys and lz4_flex for security advisories#2875

Open
skord wants to merge 1 commit into
masterfrom
mdanko/dependabot-cargo-bumps
Open

deps: bump aws-lc-sys and lz4_flex for security advisories#2875
skord wants to merge 1 commit into
masterfrom
mdanko/dependabot-cargo-bumps

Conversation

@skord
Copy link
Copy Markdown
Member

@skord skord commented Apr 21, 2026

Summary

Bumps two Rust crates via Cargo.lock only (no Cargo.toml or source changes) to close 6 high-severity Dependabot alerts:

  • aws-lc-sys 0.32.2 → 0.40.0 (via aws-lc-rs 1.14.1 → 1.16.3)
    • Closes #234, #235, #236, #247, #248 — PKCS7 bypasses, AES-CCM timing side-channel, X.509 name-constraint bypass, CRL scope check. aws-lc-sys is in the build via rustls 0.23 + rustls-webpki + jsonwebtoken 10 on the aws-lc-rs crypto provider.
  • lz4_flex 0.11.5 → 0.11.6 (plus 0.13.0 added transitively for the workspace dep)
    • Closes #245 — decompression info leak. Reachable via the parquet crate used by crates/parser to decode user-supplied parquet files.

Test plan

  • cargo build --workspace clean
  • cargo test -p parser -p json -p dekaf --lib green (covers the parquet→lz4 decode path and the dekaf lz4 encoder)
  • CI runs full workspace tests (local run blocked on live Supabase for agent sqlx queries not in the offline cache)

Resolves Dependabot high-severity alerts:
- #245 lz4_flex < 0.11.6 (decompression info leak) — reachable via
  parquet crate used by the parser
- #234, #235, #236, #247, #248 aws-lc-sys < 0.38.0/0.39.0
  (PKCS7 bypasses, AES-CCM timing, X.509 name-constraint, CRL scope)
  — in build via rustls/jsonwebtoken aws-lc-rs provider

lz4_flex: 0.11.5 -> 0.11.6 (+ 0.13.0 via workspace dep)
aws-lc-sys: 0.32.2 -> 0.40.0 (via aws-lc-rs 1.14.1 -> 1.16.3)
@skord skord self-assigned this Apr 21, 2026
@skord skord requested a review from a team April 21, 2026 22:28
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.

1 participant