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
heap-buffer-overflow at MagickCore/statistic.c:559:43 in EvaluateImages #1615
Comments
|
Thanks for the problem report. We can reproduce it and will have a patch to fix it in GIT master branch @ https://github.com/ImageMagick/ImageMagick later today. The patch will be available in the beta releases of ImageMagick @ http://www.imagemagick.org/download/beta/ by sometime tomorrow. |
|
This was assigned CVE-2019-13307. |
|
It is worth mentioning that ImageMagick/ImageMagick6@91e58d9 introduces a memory leak which is fixed later in ImageMagick/ImageMagick6@e6d26d4. Also @urban-warrior, I'm not really sure to understand the logic behind ImageMagick/ImageMagick6@643921c. What if Then there might be a mismatch between the result of |
|
We check for the maximum columns in the image sequence. |
|
Thanks for your answer. Indeed, this patch does not recreate the issue, I was confused. so, I suppose that |
|
Yes we use the thread set for two different use cases. Certainly as a convenience. Best coding practices would encourage the use of two different allocations, sized to fit, for each of these use cases. |
Prerequisites
Description
There's a heap-buffer-overflow at MagickCore/statistic.c:559:43 in EvaluateImages.
Steps to Reproduce
run_cmd:
magick -seed 0 -monitor -bias 63 "(" magick:rose -colorize 172,35,77 ")" "(" magick:logo +repage ")" -crop 507x10'!'+20-54 -evaluate-sequence Median tmpHere's ASAN log.
System Configuration
ImageMagick version:
Version: ImageMagick 7.0.8-50 Q16 x86_64 2019-06-22 https://imagemagick.org
Environment (Operating system, version and so on):
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
Additional information:
CC=clang-7 CXX=clang++-7 ./configure --disable-openmp
The text was updated successfully, but these errors were encountered: