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.
The product does not properly control the allocation and maintenance of a limited resource.
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor.
Link | Tags |
---|---|
https://bugzilla.redhat.com/show_bug.cgi?id=1939149 | issue tracking third party advisory patch |
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=25370 | issue tracking third party advisory |
https://lists.debian.org/debian-lts-announce/2021/07/msg00001.html | third party advisory mailing list |
https://security.gentoo.org/glsa/202107-27 | third party advisory vendor advisory |
https://lists.debian.org/debian-lts-announce/2022/12/msg00022.html | third party advisory mailing list |