Proposed fix here: https://github.com/uclouvain/openjpeg/issues/1347
CVE-2022-1122 (https://github.com/uclouvain/openjpeg/issues/1368): A flaw was found in the opj2_decompress program in openjpeg2 2.4.0 in the way it handles an input directory with a large number of files. When it fails to allocate a buffer to store the filenames of the input directory, it calls free() on an uninitialized pointer, leading to a segmentation fault and a denial of service.
(In reply to John Helmert III from comment #1) > CVE-2022-1122 (https://github.com/uclouvain/openjpeg/issues/1368): > > A flaw was found in the opj2_decompress program in openjpeg2 2.4.0 in the > way it handles an input directory with a large number of files. When it > fails to allocate a buffer to store the filenames of the input directory, it > calls free() on an uninitialized pointer, leading to a segmentation fault > and a denial of service. Patch here: https://github.com/uclouvain/openjpeg/commit/0afbdcf3e6d0d2bd2e16a0c4d513ee3cf86e460d
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=65217c376e5339336f01073b3312fed51654cdaf commit 65217c376e5339336f01073b3312fed51654cdaf Author: Thomas Bracht Laumann Jespersen <t@laumann.xyz> AuthorDate: 2022-03-30 20:48:59 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-04-07 02:21:39 +0000 media-libs/openjpeg: Fix segfault, security bug 832007 See: https://github.com/uclouvain/openjpeg/commit/0afbdcf3e6d0d2bd2e16a0c4d513ee3cf86e460d Bug: https://bugs.gentoo.org/832007 Signed-off-by: Thomas Bracht Laumann Jespersen <t@laumann.xyz> Closes: https://github.com/gentoo/gentoo/pull/24822 Signed-off-by: Sam James <sam@gentoo.org> .../files/openjpeg-2.4.0-r2-fix-segfault.patch | 17 +++ media-libs/openjpeg/openjpeg-2.4.0-r2.ebuild | 140 +++++++++++++++++++++ 2 files changed, 157 insertions(+)
I guess let's fork off the one with a patch into a new bug, so we can keep this open for the unfixed one upstream.
We have a fix! https://github.com/uclouvain/openjpeg/commit/7bd884f8750892de4f50bf4642fcfbe7011c6bdf
Nice! i guess it makes sense to backport the patch (mostly given that upstream doesn't cut releases that often)?
Makes sense to me! [upstream/ebuild] -> maintainer's discretion
Patch is in 2.5.2.