Skip to content

fix(deps): update aws-lc-sys and rustls-webpki for 6 RUSTSEC advisories#83

Open
joshrotenberg wants to merge 1 commit into
mainfrom
fix/aws-lc-rustsec-2026-0044-0045
Open

fix(deps): update aws-lc-sys and rustls-webpki for 6 RUSTSEC advisories#83
joshrotenberg wants to merge 1 commit into
mainfrom
fix/aws-lc-rustsec-2026-0044-0045

Conversation

@joshrotenberg
Copy link
Copy Markdown
Contributor

Summary

Cargo.lock-only update fixing six RUSTSEC advisories that have been flagged by cargo-deny on every CI Security Audit run since the advisories were published.

Crate Before After Advisories
aws-lc-rs 1.15.4 1.16.3 (transitive)
aws-lc-sys 0.37.0 0.40.0 RUSTSEC-2026-0044, RUSTSEC-2026-0045
rustls-webpki 0.103.9 0.103.13 RUSTSEC-2026-0049, -0098, -0099, -0104

Why two crates in one PR

Bumping aws-lc-sys directly was blocked: aws-lc-rs 1.15.4 pins aws-lc-sys = "^0.37.0" which excludes the patched 0.39+ range by semver. So we have to bump aws-lc-rs to 1.16.3 to relax that constraint. Once that's done, rustls-webpki advisories also surface in cargo-deny output (they were behind aws-lc errors before — same Security Audit failure surface). Bumping both together keeps the Security Audit gate green in one shot.

Pattern

Same shape as #57 (fix: update quinn-proto to 0.11.14 (RUSTSEC-2026-0037)) — focused, lockfile-only, no source code changes.

Test plan

  • cargo deny check advisoriesadvisories ok
  • cargo clippy --workspace --all-targets -- -D warnings — clean
  • cargo test --workspace — all 288 tests pass
  • cargo fmt --all -- --check — clean
  • No source files changed; only Cargo.lock

Closes #82

…,0045,0049,0098,0099,0104}

Cargo.lock-only update. Resolves six advisories that cargo-deny is
flagging on every CI Security Audit run:

  aws-lc-sys 0.37.0 -> 0.40.0 (via aws-lc-rs 1.15.4 -> 1.16.3)
    - RUSTSEC-2026-0044: X.509 Name Constraints Bypass via Wildcard/Unicode CN
    - RUSTSEC-2026-0045: Timing Side-Channel in AES-CCM Tag Verification

  rustls-webpki 0.103.9 -> 0.103.13
    - RUSTSEC-2026-0049: CRLs not considered authoritative by Distribution Point
    - RUSTSEC-2026-0098: Name constraints for URI names incorrectly accepted
    - RUSTSEC-2026-0099: Name constraints accepted for wildcard certificates
    - RUSTSEC-2026-0104: Reachable panic in CRL parsing

Bumping aws-lc-rs (rather than aws-lc-sys directly) is required because
aws-lc-rs 1.15.4 pins aws-lc-sys = "^0.37.0", which excludes the
patched 0.39+ range by semver. aws-lc-rs 1.16.3 relaxes that constraint.

`cargo deny check advisories` now passes.

Closes #82
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.

fix(deps): update aws-lc-sys to address RUSTSEC-2026-0044 and RUSTSEC-2026-0045

1 participant