A remote code execution (RCE) vulnerability exists in GIMP due to improper bounds checking during the parsing of ICNS image files. When a user opens a specially crafted ICNS file, it can trigger an out-of-bounds write, allowing attackers to execute arbitrary code within the context of the GIMP process.

A heap-based buffer-overflow in GIMP’s HDR (RGBE) file parsing allows an attacker to execute arbitrary code when a user opens or is tricked into previewing a malicious HDR file. The flaw is caused by missing length validation before copying user-supplied HDR data into a heap buffer, enabling memory corruption and control of program flow.

A heap-based buffer overflow vulnerability was discovered in GIMP’s DICOM (DCM) file parser. The flaw occurs because the application fails to properly validate the length of user-supplied data before copying it to a heap buffer. This can lead to arbitrary code execution when a user opens a specially crafted DCM image file.

A remote code execution vulnerability exists in GIMP due to improper validation of user-supplied data during the parsing of WBMP (Wireless Bitmap) files. The flaw occurs because an integer overflow can happen before memory allocation, leading to a heap-based buffer overflow. An attacker can exploit this by convincing a user to open a crafted WBMP image file or visit a malicious page, allowing arbitrary code execution within the context of the application process.

A remote code execution (RCE) vulnerability exists in GIMP’s FF file parsing functionality. The flaw stems from improper validation of user-supplied data, leading to an integer overflow before buffer allocation. When a user opens a malicious FF image file, the overflow can cause incorrect memory allocation, allowing arbitrary code execution within the context of the GIMP process. Successful exploitation requires user interaction, such as opening a crafted file, making it a local attack vector with remote delivery potential.

A stack-based buffer overflow vulnerability exists in the ILBM file parsing functionality of GIMP. When processing a specially crafted ILBM image file, improper validation of user-supplied data length before copying to a stack buffer can lead to memory corruption. Successful exploitation allows an attacker to execute arbitrary code in the context of the current process. User interaction is required, as the victim must open a malicious ILBM file.

A heap-based buffer overflow in GIMP’s X Window Dump (XWD) file parser allows an attacker to craft a malicious XWD file (or a web page that triggers opening one) that can overflow a heap buffer during parsing and lead to remote code execution in the context of the GIMP process.