Multiple code execution vulnerabilities exist in the IFFOutput::close() functionality of OpenImageIO Project OpenImageIO v2.4.4.2. A specia…
Multiple code execution vulnerabilities exist in the IFFOutput::close() functionality of OpenImageIO Project OpenImageIO v2.4.4.2. A specially crafted ImageOutput Object can lead to a heap buffer overflow. An attacker can provide malicious input to trigger these vulnerabilities.This vulnerability arises when the `xmax` variable is set to 0xFFFF and `m_spec.format` is `TypeDesc::UINT16`
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
https://cwe.mitre.org/data/definitions/122.html →Open in CWE collection →This attack forces an integer variable to go out of range. The integer variable is often used as an offset such as size of memory allocation or similarly. The attacker would typically control the value of such variable and try to get it out of range. For instance the integer in question is incremented past the maximum possible value, it may wrap to become a very small, or negative number, therefore providing a very incorrect value which can lead to unexpected behavior. At worst the attacker can execute arbitrary code.
https://capec.mitre.org/data/definitions/92.html →Open in CAPEC collection →| Product | Vendor | Status |
|---|---|---|
| openimageio | Tracked | |
| openimageio | Tracked | |
| openimageio | Tracked | |
| openimageio | Tracked | |
| openimageio | Tracked | |
| openimageio | Tracked | |
| openimageio | Tracked | |
| openimageio | Tracked | |
| openimageio | Tracked | |
| openimageio | Tracked | |
| openimageio | Tracked | |
| openimageio | Tracked | |
| debian_linux | * | Tracked |
| openimageio | * | Tracked |