From: Ross Burton Date: Mon, 23 May 2022 12:14:50 +0000 (+0100) Subject: tiff: mark CVE-2022-1622 and CVE-2022-1623 as invalid X-Git-Tag: 2022-04.2-kirkstone~110 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=4eb0b7468383a1d0314b3bfd43ea37c95de464d9;p=thirdparty%2Fopenembedded%2Fopenembedded-core.git tiff: mark CVE-2022-1622 and CVE-2022-1623 as invalid These issues only affect libtiff post-4.3.0 but before 4.4.0, caused by 3079627e and fixed by b4e79bfa. Signed-off-by: Ross Burton Signed-off-by: Richard Purdie --- diff --git a/meta/recipes-multimedia/libtiff/tiff_4.3.0.bb b/meta/recipes-multimedia/libtiff/tiff_4.3.0.bb index 9c9108a6afd..c5e964ec8c1 100644 --- a/meta/recipes-multimedia/libtiff/tiff_4.3.0.bb +++ b/meta/recipes-multimedia/libtiff/tiff_4.3.0.bb @@ -28,6 +28,9 @@ UPSTREAM_CHECK_REGEX = "tiff-(?P\d+(\.\d+)+).tar" # Tested with check from https://security-tracker.debian.org/tracker/CVE-2015-7313 # and 4.3.0 doesn't have the issue CVE_CHECK_IGNORE += "CVE-2015-7313" +# These issues only affect libtiff post-4.3.0 but before 4.4.0, +# caused by 3079627e and fixed by b4e79bfa. +CVE_CHECK_IGNORE += "CVE-2022-1622 CVE-2022-1623" inherit autotools multilib_header