Fix potential vulnerable cloned function#202
Merged
Merged
Conversation
Author
|
Hi @MrR0b0X, many thanks for merging my PR! Just want to let you know that we plan to submit this as a CVE. Please let me know if you have any concerns. |
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.
Hi again,
Our tool identified a potential overflow vulnerability in a clone function in
libopenjpeg-2.3.1/src/lib/openjp2/pi.csourced from uclouvain/openjpeg. These issues, originally reported in CVE-2016-7163, were resolved in the repository via this commit uclouvain/openjpeg@ef01f18.This PR applies the corresponding patch to fix the vulnerabilities in this codebase.
Please review at your convenience. Thank you for your time and attention!