-
Notifications
You must be signed in to change notification settings - Fork 369
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add unsound mozjpeg
#1389
Add unsound mozjpeg
#1389
Conversation
Signed-off-by: pinkforest <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Factually looks good. Style nit: The text refers to an explanation from RUSTSEC-2020-0029 but there's no link to it, I don't know how this is usually handled. As an alternative, the explanation could be inlined. Suggestion:
Affected versions of mozjpeg crate allow creating instances of any type
T
from bytes,
and do not correctly constrainT
to the types for which it is safe to do so.
Examples of safety violation possible for a typeT
:
T
contains a reference type, and it constructs a pointer to an invalid, arbitrary memory address.T
requires a safety and/or validity invariant for its construction that may be violated.
Signed-off-by: pinkforest <[email protected]>
Thanks - we use EDIT: Also added link in the .md EDIT.2: Also added function signature |
Signed-off-by: pinkforest <[email protected]>
Signed-off-by: pinkforest <[email protected]>
Signed-off-by: pinkforest <[email protected]>
Signed-off-by: pinkforest <[email protected]>
Closes #327
ImageOptim/mozjpeg-rust#10
@HeroicKatora would you mind reviewing this ? thx