Skip to content
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 WriteMAPImage #573

Closed
jgj212 opened this issue Jul 17, 2017 · 2 comments
Closed

memory leak in WriteMAPImage #573

jgj212 opened this issue Jul 17, 2017 · 2 comments
Labels

Comments

@jgj212
Copy link
Contributor

jgj212 commented Jul 17, 2017

Version: ImageMagick 7.0.6-2 Q16 x86_64

./magick convert $FILE  out.map
==12299==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 3 byte(s) in 1 object(s) allocated from:
    #0 0x4deeb6 in __interceptor_malloc asan_malloc_linux.cc:66
    #1 0x7f9e4bb7a186 in AcquireMagickMemory memory.c:464:10
    #2 0x7f9e4bb7a1e8 in AcquireQuantumMemory memory.c:537:10
    #3 0x7f9e4bf5e0a3 in WriteMAPImage map.c:390:30
    #4 0x7f9e4b9596fe in WriteImage constitute.c:1114:14
    #5 0x7f9e4b95a5fd in WriteImages constitute.c:1333:13
    #6 0x7f9e4b005900 in ConvertImageCommand convert.c:3280:11
    #7 0x7f9e4b1540cf in MagickCommandGenesis mogrify.c:183:14
    #8 0x514a37 in MagickMain magick.c:149:10
    #9 0x514491 in main magick.c:180:10
    #10 0x7f9e45991f44 in __libc_start_main libc-start.c:287

POC: https://github.com/jgj212/poc/blob/master/leak-WriteMAPImage

Credit : ADLab of Venustech

@mikayla-grace
Copy link

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.

@nohmask
Copy link

nohmask commented Sep 8, 2017

This was assigned CVE-2017-12663.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

4 participants