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
memory leak in WriteJNGImage #667
Labels
Comments
|
YIkes. I confirm that it's bad. It has made my workstation nonresponsive
--no keyboard or mouse, lots of disk activity sound, no ssh access. After about
half an hour my computer shut itself down.
|
|
That was pilot error. My "try.sh" script contained "try.sh" so it was just
filling up my machine with instances of "try.sh". Once that was fixed,
it attempts a large malloc, then finds EOF. The image is actually an SFW-95
Seattle Film Works) file.
…On Thu, Aug 10, 2017 at 2:36 PM, Glenn Randers-Pehrson ***@***.***> wrote:
YIkes. I confirm that it's bad. It has made my workstation nonresponsive
--no keyboard or mouse, lots of disk activity sound, no ssh access.
|
|
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 @ https://www.imagemagick.org/download/beta/ by sometime tomorrow. |
dlemstra
pushed a commit
that referenced
this issue
Aug 10, 2017
dlemstra
added a commit
that referenced
this issue
Aug 18, 2017
|
Please use CVE-2017-13059 for this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version: ImageMagick 7.0.6-6 Q16 x86_64
A memory leak vulnerability was found in function WriteJNGImage in coders/png.c,which allow attackers to cause a denial of service via a crafted file.
testcase:https://github.com/bestshow/p0cs/blob/master/memory_leak_in_WriteJNGImage
Credit:ADLab of Venustech
The text was updated successfully, but these errors were encountered: