From 70c2ad9bca8e481470ac0a543b3ceb5b3827a303 Mon Sep 17 00:00:00 2001 From: Ross Burton Date: Mon, 23 May 2022 13:14:50 +0100 Subject: 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. (From OE-Core rev: 49e93892a37d1a2af2b0a155117441e978385e4c) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie --- meta/recipes-multimedia/libtiff/tiff_4.3.0.bb | 3 +++ 1 file changed, 3 insertions(+) (limited to 'meta/recipes-multimedia/libtiff') diff --git a/meta/recipes-multimedia/libtiff/tiff_4.3.0.bb b/meta/recipes-multimedia/libtiff/tiff_4.3.0.bb index 9c9108a6af..c5e964ec8c 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 -- cgit v1.2.3-54-g00ecf