Add advisory for stainless_ffmpeg FormatContext stream_index unsoundness#2987
Open
sisy2020 wants to merge 1 commit into
Open
Add advisory for stainless_ffmpeg FormatContext stream_index unsoundness#2987sisy2020 wants to merge 1 commit into
sisy2020 wants to merge 1 commit into
Conversation
Member
|
Waiting for maintainer confirmation. |
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.
Affected crate(s)
stainless_ffmpeg(634 recent downloads per crates.io)Links to upstream issue(s) or PR(s)
Severity
This advisory classifies the issue as informational
unsound. Affected versions exposed safe publicFormatContextmethods that accepted astream_indexparameter and used it in unsafe pointer operations without checking whether the index was valid. Safe callers could pass a negative or out-of-boundsstream_index, which could trigger undefined behavior without usingunsafe.The issue was fixed upstream in
0.6.0by marking the affected methods asunsafeand documenting the caller's safety requirement.Checklist
RUSTSEC-0000-0000as the IDdatefield is set to the public disclosure date