chacha20: mark v0.10.0 and v0.10.1 as yanked - #583
Merged
Conversation
IceTDrinker
added a commit
to zama-ai/tfhe-rs
that referenced
this pull request
Aug 28, 2026
- RustCrypto/stream-ciphers#583 (yank) - RustCrypto/stream-ciphers#580 (UB SSE2 backend) - RustCrypto/utils#1513 (MIRI stuff enabled)
mycodedoesnotcompile2
pushed a commit
to mycodedoesnotcompile2/arti_mirror
that referenced
this pull request
Aug 31, 2026
Updates chacha20 from 0.10.1 to 0.10.2, as the previous version got yanked from crates.io and now cargo-audit is complaining. Apparently the reason for this fix was the accidential use of undefined behavior in the previous release: <RustCrypto/stream-ciphers#583>
This was referenced Aug 31, 2026
zerosnacks
added a commit
to selemis-com/kival
that referenced
this pull request
Sep 2, 2026
Replace the yanked chacha20 0.10.0 release with 0.10.2 in Cargo.lock. The affected releases contain undefined behavior in the SSE2 backend. The underlying bug was fixed in: RustCrypto/stream-ciphers#580 The affected 0.10.0 and 0.10.1 releases were subsequently yanked in: RustCrypto/stream-ciphers#583
This was referenced Sep 5, 2026
Hmbown
pushed a commit
to Hmbown/Codewhale
that referenced
this pull request
Sep 8, 2026
Update only chacha20 0.10.1 to 0.10.2 in Cargo.lock. RustCrypto yanked 0.10.0/0.10.1 for an SSE4.1 intrinsic used in the SSE2 RNG/legacy backend, which is undefined behavior when that target feature is unavailable. The patch preserves MSRV 1.85, enabled dependency edges, and public features. The lockfile route is oauth2 -> reqwest 0.12 -> optional QUIC -> quinn-proto -> rand 0.10 -> chacha20. No chacha20 edge is active in this workspace's all-features/all-targets cargo tree; this does not assert observed exploitation. Bincode/yaml-rust maintenance warnings and existing audit policy are unchanged. Validation: cargo update --offline --precise 0.10.2 succeeded; structural lock comparison confirms exactly one version/checksum change, all other entries and edges unchanged; locked offline all-features/all-targets dependency resolution passed; cargo audit --no-fetch: 0 vulnerabilities, 0 yanked crates, 2 existing maintenance warnings; git diff --check passed. No Rust build/tests or hosted CI run for this dormant lock-only dependency. Core root has no npm test/check:web scripts. No new advisory ignores. Upstream: RustCrypto/stream-ciphers#583 Fix: RustCrypto/stream-ciphers#580 Release: https://github.com/RustCrypto/stream-ciphers/releases/tag/chacha20-v0.10.2
link2xt
added a commit
to chatmail/core
that referenced
this pull request
Sep 10, 2026
0.10.1 is yanked: RustCrypto/stream-ciphers#583
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.
The yanked versions contain UB in SSE2 backend, see #580.