Back to bug 2019783
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Dhananjay Arunesh | 2021-11-03 10:53:56 UTC | Depends On | 2019785, 2019784 | |
| Dhananjay Arunesh | 2021-11-03 11:10:46 UTC | Blocks | 2013538 | |
| Todd Cullum | 2021-11-04 00:08:38 UTC | CC | rh-spice-bugs | |
| Todd Cullum | 2021-11-04 21:38:13 UTC | Depends On | 2020446, 2020445, 2020444 | |
| Marian Rehak | 2021-11-08 12:15:08 UTC | Alias | CVE-2021-3933 | |
| Summary | openexr: Integer-overflow in Imf_3_1::bytesPerDeepLineTable | CVE-2021-3933 openexr: Integer-overflow in Imf_3_1::bytesPerDeepLineTable | ||
| Marian Rehak | 2021-11-08 12:19:20 UTC | Blocks | 2021121 | |
| Todd Cullum | 2021-11-09 02:27:42 UTC | Fixed In Version | OpenEXR 3.1.2 | |
| Marian Rehak | 2022-03-25 09:58:59 UTC | Doc Text | An integer overflow could occur when OpenEXR processes a crafted file on systems where size_t < 64 bits. This could cause an invalid bytesPerLine and maxBytesPerLine value, which could lead to problems with application stability or lead to other attack paths. | |
| RaTasha Tillery-Smith | 2022-03-25 13:20:18 UTC | Doc Text | An integer overflow could occur when OpenEXR processes a crafted file on systems where size_t < 64 bits. This could cause an invalid bytesPerLine and maxBytesPerLine value, which could lead to problems with application stability or lead to other attack paths. | An integer overflow could occur when OpenEXR processes a crafted file on systems where size_t is less than 64 bits. This issue could cause an invalid bytesPerLine and maxBytesPerLine value, which leads to problems with application stability or other attack paths. |
| Red Hat Bugzilla | 2023-07-07 08:30:06 UTC | Assignee | security-response-team | nobody |
Back to bug 2019783