Yangy-Xiao

The issue is related to a "use of uninitialized value" in the `ReadCUTImage` function in `coders/cut.c`. It is also described as a vulnerability due to insufficient input validation in the `ReadCUTImage` function, which could allow a remote attacker to access confidential information or cause a denial of service.

The issue is related to a memory leak in the ReadBMPImage function located in coders/bmp.c.

The issue is related to a memory leak in the ReadPSImage function in coders/ps.c.

The issue is related to a memory leak in the function ReadVIFFImage in coders/viff.c.

The issue is related to the use of an uninitialized value in the WriteJP2Image function in coders/jp2.c. This vulnerability is associated with incorrect initialization, which can be exploited by a remote attacker to gain access to confidential information or cause a denial of service.

The issue is related to a memory leak in the ReadPCLImage function, located in coders/pcl.c.

The issue is related to a memory leak in the WriteDPXImage function, located in coders/dpx.c.

The issue is related to the use of an uninitialized value in the `SyncImageSettings` function in `MagickCore/image.c`, which is also connected to `AcquireImage` in `magick/image.c`. This could potentially allow an attacker to impact the confidentiality, integrity, and availability of protected information.

The issue is related to the use of an uninitialized value in the ReadPANGOImage function in coders/pango.c, which can lead to incorrect initialization. This can potentially allow a remote attacker to access confidential information or cause a denial of service.

The issue is caused by an integer overflow in the TIFFSeekCustomStream function. This can be exploited by a remote attacker to cause a denial of service by providing large input data.

The issue is related to a missing check for length in the `ReadDCMImage` and `ReadPICTImage` functions, which can be exploited by remote attackers to cause a denial of service via a crafted image. This is due to insufficient input validation, allowing an attacker to disrupt service with a specially crafted file.

The issue is related to a memory leak in the function ReadOneJNGImage, located in coders/png.c.

The issue is related to a memory leak in the TIFFWritePhotoshopLayers function, located in coders/tiff.c.

The issue is related to excessive memory allocation in the `ReadBMPImage` and `ReadDIBImage` functions, which can be exploited by remote attackers to cause a denial of service using a specially crafted image file. This can lead to a denial of service.

An issue in OpenJPEG allows for a heap-based buffer overflow due to missing checks for `header info.height` and `header info.width` in the `pnmtoimage` function in `bin/jpwl/convert.c`.

A heap-based buffer overflow was discovered in the `t2 encode packet` function in `lib/openmj2/t2.c`, causing an out-of-bounds write. This may lead to remote denial of service or possibly other unspecified impact.

The issue is related to division-by-zero errors in the `pi next pcrl`, `pi next cprl`, and `pi next rpcl` functions in the `lib/openjp3d/pi.c` file of the OpenJPEG library. This can be exploited by a remote attacker to cause a denial of service, resulting in an application crash.

The issue is related to the functions `ReadDCMImage`, `ReadPWPImage`, `ReadCALSImage`, and `ReadPICTImage` in the components `coders/dcm.c`, `coders/pwp.c`, `coders/cals.c`, and `coders/pict.c`, which do not check the return value of the `fputc` function. This allows remote attackers to cause a denial of service via a crafted image file. The exploitation of this issue can lead to a disruption in service.

The issue is related to a heap-based buffer over-read in the `Exiv2::Internal::PngChunk::keyTXTChunk` function of `pngchunk int.cpp`. This can be exploited by a crafted PNG file, potentially leading to a remote denial of service attack. The vulnerability is associated with a buffer overflow, which may allow a remote attacker to cause a service disruption.

The issue is related to a NULL pointer dereference in the `imagetobmp` function of `convertbmp.c` at line 980. Specifically, `image->comps[0].data` is not assigned a value after initialization, which remains `NULL`. This results in a Denial of Service impact.