From: Peter Marko Date: Sun, 25 Aug 2024 21:41:44 +0000 (+0200) Subject: libyaml: Ignore CVE-2024-35325 X-Git-Tag: yocto-5.2~1964 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=c97f00d122f60501751625e27b9c70166396d754;p=thirdparty%2Fopenembedded%2Fopenembedded-core-contrib.git libyaml: Ignore CVE-2024-35325 This is similar CVE as the previous ones from the same author. https://github.com/yaml/libyaml/issues/303 explain why this is misuse (or wrong use) of libyaml. Signed-off-by: Peter Marko Signed-off-by: Richard Purdie --- diff --git a/meta/recipes-support/libyaml/libyaml_0.2.5.bb b/meta/recipes-support/libyaml/libyaml_0.2.5.bb index 334d9113d22..aa7fc5e9145 100644 --- a/meta/recipes-support/libyaml/libyaml_0.2.5.bb +++ b/meta/recipes-support/libyaml/libyaml_0.2.5.bb @@ -18,6 +18,7 @@ inherit autotools DISABLE_STATIC:class-nativesdk = "" DISABLE_STATIC:class-native = "" +CVE_STATUS[CVE-2024-35325] = "upstream-wontfix: Upstream thinks this is a misuse (or wrong use) of the libyaml API - https://github.com/yaml/libyaml/issues/303" CVE_STATUS[CVE-2024-35326] = "upstream-wontfix: Upstream thinks there is no working code that is exploitable - https://github.com/yaml/libyaml/issues/302" CVE_STATUS[CVE-2024-35328] = "upstream-wontfix: Upstream thinks there is no working code that is exploitable - https://github.com/yaml/libyaml/issues/302"