pkgs: bump buzz-agent-tools to cc8a8b0d - clears RUSTSEC-2026-0258 - #7
Closed
axlroden wants to merge 1 commit into
Closed
pkgs: bump buzz-agent-tools to cc8a8b0d - clears RUSTSEC-2026-0258#7axlroden wants to merge 1 commit into
axlroden wants to merge 1 commit into
Conversation
h2 was pinned at 0.4.14, vulnerable to unbounded empty DATA frames (low severity DoS - excessive memory or an integer-overflow panic on an unconsumed stream). Fixed upstream in block/buzz#6222, merged into this commit, which brings the vendored lock to h2 0.4.16. pkgs/Cargo.lock is the whole workspace's lockfile, not scoped to the three crates this derivation builds, so the diff also carries three weeks of ordinary dependency churn elsewhere in the tree alongside the h2 fix. nix flake check --no-build passes against the new rev.
Owner
Author
|
Superseded by the minimal verified lockfile/package-vendoring fix merged to master as d34e1a9. This source-pin branch regresses to an ancestor for the nostr binary population and must not be merged. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Bumps
buzz-agent-tools(buzz-acp,buzz-cli,git-credential-nostr) from631b05c883f58e9533e9038b4669ebdfb1d9cf27(2026-08-04) tocc8a8b0dcbf5c01311b2ac7e1827ff3e582299f3(2026-08-18), the merge commit forblock/buzz#6222, which bumps the workspace's own
h2to 0.4.16.Why
h2was locked at 0.4.14, in scope forRUSTSEC-2026-0258: unbounded empty
DATA frames are accepted and queued without limit, which can grow memory unboundedly or
panic on integer overflow if a stream is never consumed. Severity is low, and both binaries
we build are HTTP/2 clients (they connect out to a relay) rather than servers, so exposure
here is a compromised or misbehaving relay - not zero, so worth clearing rather than
skipping since it's cheap.
Notes
pkgs/Cargo.lockis the upstream workspace's own lockfile, vendored whole rather thanscoped to the three crates this derivation builds, so the diff also carries three weeks of
ordinary dependency churn elsewhere in the tree alongside the
h2fix - not something toread line by line.
nix flake check --no-build .passes against the new rev/hash.