There's a flaw in OpenEXR's scanline input file functionality in versions before 3.0.0-beta. An attacker able to submit a crafted file to be processed by OpenEXR could consume excessive system memory. The greatest impact of this flaw is 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=1939160 | patch third party advisory issue tracking |
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=27409 | third party advisory issue tracking |
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 |