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 WritePCXImage #1049

Closed
3 tasks done
jgj212 opened this issue Mar 24, 2018 · 3 comments
Closed
3 tasks done

Memory leak in WritePCXImage #1049

jgj212 opened this issue Mar 24, 2018 · 3 comments
Labels

Comments

@jgj212
Copy link
Contributor

jgj212 commented Mar 24, 2018

Prerequisites

  • I have written a descriptive issue title
  • I have verified that I am using the latest version of ImageMagick
  • I have searched open and closed issues to ensure it has not already been reported

Description

Memory leak in WritePCXImage

Steps to Reproduce

      page_table=(MagickOffsetType *) AcquireQuantumMemory(1024UL,  		//line 923, allocation for page_table
        sizeof(*page_table));
      if (page_table == (MagickOffsetType *) NULL)
        ThrowWriterException(ResourceLimitError,"MemoryAllocationFailed");
    pcx_colormap=(unsigned char *) AcquireQuantumMemory(256UL,
      3*sizeof(*pcx_colormap));
    if (pcx_colormap == (unsigned char *) NULL)
      ThrowWriterException(ResourceLimitError,"MemoryAllocationFailed"); 	//line 1001, memory leak as not free page_table

System Configuration

  • ImageMagick version: 7.0.7-28
  • Environment (Operating system, version and so on): Ubuntu14.04 x86_64
  • Additional information:

Credit: ADLab of Venustech

@urban-warrior
Copy link
Member

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 dlemstra added the bug label Mar 24, 2018
@nohmask
Copy link

nohmask commented Oct 9, 2018

This was assigned CVE-2018-18016.

@octes
Copy link

octes commented Oct 10, 2018

Hi,
does anyone know what the relation to CVE-2017-13058 (#666) is. The fix seems similar.

Thanks

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

5 participants