CVE-2019-7398

In ImageMagick before 7.0.8-25, a memory leak exists in WriteDIBImage in coders/dib.c.

The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory.

Name	Vendor	Start Version	End Version
Imagemagick	Imagemagick	*	6.9.10-25 (excluding)
Imagemagick	Imagemagick	7.0.0-0 (including)	7.0.8-25 (excluding)
Red Hat Enterprise Linux 7	RedHat	autotrace-0:0.31.1-38.el7	*
Red Hat Enterprise Linux 7	RedHat	emacs-1:24.3-23.el7	*
Red Hat Enterprise Linux 7	RedHat	ImageMagick-0:6.9.10.68-3.el7	*
Red Hat Enterprise Linux 7	RedHat	inkscape-0:0.92.2-3.el7	*
Imagemagick	Ubuntu	bionic	*
Imagemagick	Ubuntu	cosmic	*
Imagemagick	Ubuntu	devel	*
Imagemagick	Ubuntu	disco	*
Imagemagick	Ubuntu	focal	*
Imagemagick	Ubuntu	jammy	*
Imagemagick	Ubuntu	kinetic	*
Imagemagick	Ubuntu	lunar	*
Imagemagick	Ubuntu	mantic	*
Imagemagick	Ubuntu	noble	*
Imagemagick	Ubuntu	oracular	*
Imagemagick	Ubuntu	trusty	*
Imagemagick	Ubuntu	trusty/esm	*
Imagemagick	Ubuntu	xenial	*

Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone.
For example, glibc in Linux provides protection against free of invalid pointers.
When using Xcode to target OS X or iOS, enable automatic reference counting (ARC) [REF-391].
To help correctly and consistently manage memory when programming in C++, consider using a smart pointer class such as std::auto_ptr (defined by ISO/IEC ISO/IEC 14882:2003), std::shared_ptr and std::unique_ptr (specified by an upcoming revision of the C++ standard, informally referred to as C++ 1x), or equivalent solutions such as Boost.

NVD	https://nvd.nist.gov/vuln/detail/CVE-2019-7398
CWE	https://cwe.mitre.org/data/definitions/401.html

Missing Release of Memory after Effective Lifetime