libyaml: Update status of CVE-2024-35328
PATCH 1/1 libyaml: Update status of CVE-2024-35328
This is open yet but seems to be disputed
--- meta/recipes-support/libyaml/libyaml_0.2.5.bb | 2 ++ 1 file changed, 2 insertions(+)
meta/recipes-support/libyaml/libyaml_0.2.5.bb +2 -0
@@ -18,4 +18,6 @@ inherit autotools DISABLE_STATIC:class-nativesdk = "" DISABLE_STATIC:class-native = "" +CVE_STATUS[CVE-2024-35328] = "disputed: Upstream thinks there is no working code that is exploitable - https://github.com/yaml/libyaml/issues/302" + BBCLASSEXTEND = "native nativesdk"
Quoted 22 lines · Khem Raj via lists.openembedded.org
This is open yet but seems to be disputed
Signed-off-by Khem Raj <[email protected]>--- meta/recipes-support/libyaml/libyaml_0.2.5.bb | 2 ++ 1 file changed, 2 insertions(+)meta/recipes-support/libyaml/libyaml_0.2.5.bb +1
-0@@ -18,4 +18,6 @@ inherit autotools DISABLE_STATIC:class-nativesdk = "" DISABLE_STATIC:class-native = "" +CVE_STATUS[CVE-2024-35328] = "disputed: Upstream thinks there is noworking code that is exploitable -
https://github.com/yaml/libyaml/issues/302"
+
BBCLASSEXTEND = "native nativesdk"
Quoted 1 line
Khem, formally this one isn't "disputed". "disputed" is a formal CVE
programme tag, which isn't there for CVE-2024-35328 as of today.
Regards,
Marta
Quoted 21 lines · Marta Rybczynska
Quoted 16 lines · Khem Raj via lists.openembedded.org
This is open yet but seems to be disputed
Signed-off-by Khem Raj <[email protected]>--- meta/recipes-support/libyaml/libyaml_0.2.5.bb | 2 ++ 1 file changed, 2 insertions(+)meta/recipes-support/libyaml/libyaml_0.2.5.bb +0
-0@@ -18,4 +18,6 @@ inherit autotools DISABLE_STATIC:class-nativesdk = "" DISABLE_STATIC:class-native = ""
Quoted 9 lines
Quoted 7 lines
meta/recipes-support/libyaml/libyaml_0.2.5.bb +1
-0+CVE_STATUS[CVE-2024-35328] = "disputed: Upstream thinks there is noworking code that is exploitable -
https://github.com/yaml/libyaml/issues/302"
+
BBCLASSEXTEND = "native nativesdk"Khem, formally this one isn't "disputed". "disputed" is a formal CVE
programme tag, which isn't there for CVE-2024-35328 as of today.
Fair enough. We shall change it. Is ignored ok ?
Quoted 5 lines
Regards,
Marta
Quoted 32 lines · Khem Raj
Quoted 27 lines · Marta Rybczynska
Quoted 22 lines · Khem Raj via lists.openembedded.org
This is open yet but seems to be disputed
Signed-off-by Khem Raj <[email protected]>--- meta/recipes-support/libyaml/libyaml_0.2.5.bb | 2 ++ 1 file changed, 2 insertions(+)meta/recipes-support/libyaml/libyaml_0.2.5.bb +1
-0@@ -18,4 +18,6 @@ inherit autotools DISABLE_STATIC:class-nativesdk = "" DISABLE_STATIC:class-native = "" +CVE_STATUS[CVE-2024-35328] = "disputed: Upstream thinks there is noworking code that is exploitable -
https://github.com/yaml/libyaml/issues/302"
+
BBCLASSEXTEND = "native nativesdk"
Quoted 6 lines
Quoted 3 lines
Quoted 1 line
Khem, formally this one isn't "disputed". "disputed" is a formal CVE
programme tag, which isn't there for CVE-2024-35328 as of today.
Fair enough. We shall change it. Is ignored ok ?
Wontfix will do for now. If the libyaml team has asked for a refusal and it will be granted, they might be even removed. But this is a direct MITRE filling, so will take time.
Regards,
Marta