Advisory: sodiumoxide degenerate public keys#4
Merged
Conversation
5b8a684 to
2d75a22
Compare
Fixed in sodiumoxide 0.0.14. See: https://github.com/dnaq/sodiumoxide/issues/154
2d75a22 to
1a18a42
Compare
Member
Author
|
This has been filed as |
berkant-koc
pushed a commit
to berkant-koc/advisory-db
that referenced
this pull request
May 17, 2026
Maintainer @spearman published v0.3.0 on 2026-05-16 with the fix plus regression test race_disconnect_does_not_corrupt_sender_or_abort (commit 2714da2), accepted GHSA-6m57-8r3p-pqx6, and closed upstream issue rustsec#4. All prior versions (0.2.0, 0.1.x) are yanked on crates.io. - patched = [">= 0.3.0"] - aliases = ["GHSA-6m57-8r3p-pqx6"] - url = spearman/unbounded-spsc#4
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
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.
Fixed in sodiumoxide 0.0.14 (cc @dnaq)
See: https://github.com/dnaq/sodiumoxide/issues/154
This commit also serves as a sort of archetype for filing future security advisories.
It proposes a
RUSTSEC-YYYY-NNNNformat for identifying advisories. Ideally we'd use Distributed Weakness Filing for this purpose, but I've been having trouble getting ahold of the DWF maintainer to move forward on that (cc @kurtseifried)However, we can adopt the
RUSTSEC-...scheme for now, then refile vulnerabilities under DWF if and when we get a block assigned (RubySec, as an example, has had to refile vulnerabilities this way several times)