Add advisory for http-types: violated ASCII invariants#2923
Merged
Conversation
Member
|
Pinged in the upstream issue. Feel free to ping me again if there's been no response in 4 weeks. (Looks like the "Severity" section contains a copy/pasta error.) |
djc
reviewed
Jun 4, 2026
| This issue has not been confirmed as Undefined Behavior, but the unsafe | ||
| justification in `Authorization::value` and `WwwAuthenticate::value` appears incorrect and can produce values outside the expected ASCII-only constraints. | ||
|
|
||
| ## Example |
Removed details about an unpatched issue and example code from the RUSTSEC-0000-0000.md file, indicating the crate is unmaintained.
Contributor
Author
|
@djc Thank you for your feedback! I have modified the rustsec markdown. |
djc
approved these changes
Jun 8, 2026
Member
|
Thanks! |
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
2 participants
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.
Affected crate(s)
Links to upstream issue(s) or PR(s)
Severity
Soundness issue: safe parsing bypasses the DNSKEY RDATA 16-bit length invariant, allowing construction of invalid records and violating new_unchecked safety preconditions, which can undermine memory safety assumptions.
Checklist
RUSTSEC-0000-0000as the IDdatefield is set to the public disclosure dateThis repo is active, but the issue has no reply for more than two months. Although this crate has published new version, the ths same soundness issues exist.