Total
54 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2021-3479 | 2 Debian, Openexr | 2 Debian Linux, Openexr | 2022-12-13 | 4.3 MEDIUM | 5.5 MEDIUM |
| There's a flaw in OpenEXR's Scanline API functionality in versions before 3.0.0-beta. An attacker who is able to submit a crafted file to be processed by OpenEXR could trigger excessive consumption of memory, resulting in an impact to system availability. | |||||
| CVE-2021-20296 | 2 Debian, Openexr | 2 Debian Linux, Openexr | 2022-12-13 | 5.0 MEDIUM | 5.3 MEDIUM |
| A flaw was found in OpenEXR in versions before 3.0.0-beta. A crafted input file supplied by an attacker, that is processed by the Dwa decompression functionality of OpenEXR's IlmImf library, could cause a NULL pointer dereference. The highest threat from this vulnerability is to system availability. | |||||
| CVE-2021-20304 | 1 Openexr | 1 Openexr | 2022-12-07 | N/A | 7.5 HIGH |
| A flaw was found in OpenEXR's hufDecode functionality. This flaw allows an attacker who can pass a crafted file to be processed by OpenEXR, to trigger an undefined right shift error. The highest threat from this vulnerability is to system availability. | |||||
| CVE-2021-26945 | 1 Openexr | 1 Openexr | 2022-10-19 | 4.3 MEDIUM | 5.5 MEDIUM |
| An integer overflow leading to a heap-buffer overflow was found in OpenEXR in versions before 3.0.1. An attacker could use this flaw to crash an application compiled with OpenEXR. | |||||
| CVE-2017-9113 | 1 Openexr | 1 Openexr | 2020-08-30 | 4.3 MEDIUM | 8.8 HIGH |
| In OpenEXR 2.2.0, an invalid write of size 1 in the bufferedReadPixels function in ImfInputFile.cpp could cause the application to crash or execute arbitrary code. | |||||
| CVE-2017-9112 | 1 Openexr | 1 Openexr | 2020-08-30 | 4.3 MEDIUM | 6.5 MEDIUM |
| In OpenEXR 2.2.0, an invalid read of size 1 in the getBits function in ImfHuf.cpp could cause the application to crash. | |||||
| CVE-2017-9115 | 1 Openexr | 1 Openexr | 2020-08-30 | 6.8 MEDIUM | 8.8 HIGH |
| In OpenEXR 2.2.0, an invalid write of size 2 in the = operator function in half.h could cause the application to crash or execute arbitrary code. | |||||
| CVE-2017-9114 | 1 Openexr | 1 Openexr | 2020-08-30 | 4.3 MEDIUM | 6.5 MEDIUM |
| In OpenEXR 2.2.0, an invalid read of size 1 in the refill function in ImfFastHuf.cpp could cause the application to crash. | |||||
| CVE-2017-12596 | 1 Openexr | 1 Openexr | 2020-08-30 | 6.8 MEDIUM | 7.8 HIGH |
| In OpenEXR 2.2.0, a crafted image causes a heap-based buffer over-read in the hufDecode function in IlmImf/ImfHuf.cpp during exrmaketiled execution; it may result in denial of service or possibly unspecified other impact. | |||||
| CVE-2017-9110 | 1 Openexr | 1 Openexr | 2020-08-30 | 4.3 MEDIUM | 6.5 MEDIUM |
| In OpenEXR 2.2.0, an invalid read of size 2 in the hufDecode function in ImfHuf.cpp could cause the application to crash. | |||||
| CVE-2017-9111 | 1 Openexr | 1 Openexr | 2020-08-30 | 6.8 MEDIUM | 8.8 HIGH |
| In OpenEXR 2.2.0, an invalid write of size 8 in the storeSSE function in ImfOptimizedPixelReading.h could cause the application to crash or execute arbitrary code. | |||||
| CVE-2017-9116 | 1 Openexr | 1 Openexr | 2020-08-30 | 4.3 MEDIUM | 6.5 MEDIUM |
| In OpenEXR 2.2.0, an invalid read of size 1 in the uncompress function in ImfZip.cpp could cause the application to crash. | |||||
| CVE-2009-1720 | 1 Openexr | 1 Openexr | 2012-10-23 | 7.5 HIGH | N/A |
| Multiple integer overflows in OpenEXR 1.2.2 and 1.6.1 allow context-dependent attackers to cause a denial of service (application crash) or possibly execute arbitrary code via unspecified vectors that trigger heap-based buffer overflows, related to (1) the Imf::PreviewImage::PreviewImage function and (2) compressor constructors. NOTE: some of these details are obtained from third party information. | |||||
| CVE-2009-1722 | 1 Openexr | 1 Openexr | 2012-10-23 | 6.8 MEDIUM | N/A |
| Heap-based buffer overflow in the compression implementation in OpenEXR 1.2.2 allows context-dependent attackers to cause a denial of service (application crash) or possibly execute arbitrary code via unspecified vectors. | |||||