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 ReadDCMImage #551

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

memory leak in ReadDCMImage #551

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

Comments

@jgj212
Copy link
Contributor

jgj212 commented Jul 9, 2017

Version: ImageMagick 7.0.6-1 Q16 x86_64

#./magick identify $FILE

=================================================================
==2953==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 168 byte(s) in 1 object(s) allocated from:
    #0 0x4def96 in __interceptor_malloc asan_malloc_linux.cc:66
    #1 0x7f7ad266ef76 in AcquireMagickMemory memory.c:463:10
    #2 0x7f7ad2982f84 in ReadDCMImage dcm.c:3073:33
    #3 0x7f7ad245ef98 in ReadImage constitute.c:497:13
    #4 0x7f7ad27d5bd9 in ReadStream stream.c:1045:9
    #5 0x7f7ad245db3f in PingImage constitute.c:226:9
    #6 0x7f7ad245e2e3 in PingImages constitute.c:327:10
    #7 0x7f7ad1bbf126 in IdentifyImageCommand identify.c:319:18
    #8 0x7f7ad1c7cdff in MagickCommandGenesis mogrify.c:183:14
    #9 0x514f77 in MagickMain magick.c:151:10
    #10 0x5149d1 in main magick.c:263:10
    #11 0x7f7acc4baf44 in __libc_start_main libc-start.c:287

SUMMARY: AddressSanitizer: 168 byte(s) leaked in 1 allocation(s).

testcase: https://github.com/jgj212/poc/blob/master/leak-ReadDCMImage

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-12644.

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