Prevent SIGABRT on excessive subBox length in jp2image.cpp #470
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.
This fixes CVE-2018-9145
I am working on analyzing CVEs for the Debian LTS team and I believe I have identified the fix for CVE-2018-9145. Note that while I gave the MITRE URL in the test I added, the reproducer originates here: https://github.com/xiaoqx/pocs/tree/master/exiv2 (it is reproducer 4 that I used).
The fix that I applied in
jp2image.cpp
follows the same pattern as the length check atjp2image.cpp:272
.Also note that as a result of changes in #368 the reproducer produces the output
Uncaught exception: std::bad_alloc
atexiv2.cpp:177
instead of aSIGABRT
.If I need to adjust anything in this pull request, please let me know.