Message ID | 20240801101719.89910-1-niko.mauno@vaisala.com |
---|---|
State | Accepted, archived |
Commit | c66d9a2a0d197498fa21ee8ca51a4afb59f75473 |
Headers | show |
Series | libyaml: Amend CVE status as 'upstream-wontfix' | expand |
I wonder if it would be good to backport this to Scarthgap. I'm getting the following warning for unpatched CVE on latest scarthgap: WARNING: libyaml-0.2.5-r0 do_cve_check: Found unpatched CVE (CVE-2024-35328), for more information check /home/builder/yocto/build/tmp/work/cortexa9t2hf-neon-tdx-linux-gnueabi/libyaml/0.2.5/temp/cve.log Would this patch silence it?
On 8/2/24 17:25, Guðni Már Gilbert wrote: > I wonder if it would be good to backport this to Scarthgap. I'm getting > the following warning for unpatched CVE on latest scarthgap: > WARNING: libyaml-0.2.5-r0 do_cve_check: Found unpatched CVE > (CVE-2024-35328), for more information check > /home/builder/yocto/build/tmp/work/cortexa9t2hf-neon-tdx-linux-gnueabi/libyaml/0.2.5/temp/cve.log > Would this patch silence it? > Thanks, I've submitted https://lists.openembedded.org/g/openembedded-core/message/202933 which should fix the issue if it gets incorporated. -Niko
diff --git a/meta/recipes-support/libyaml/libyaml_0.2.5.bb b/meta/recipes-support/libyaml/libyaml_0.2.5.bb index 2154910d0c..1c6a5fcb45 100644 --- a/meta/recipes-support/libyaml/libyaml_0.2.5.bb +++ b/meta/recipes-support/libyaml/libyaml_0.2.5.bb @@ -18,6 +18,6 @@ inherit autotools DISABLE_STATIC:class-nativesdk = "" DISABLE_STATIC:class-native = "" -CVE_STATUS[CVE-2024-35328] = "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" BBCLASSEXTEND = "native nativesdk"