qemu: Whitelist CVE
PATCH 1/1 qemu: Whitelist CVE
Reason:
CVE-2021-3947, issue introduced in v6.0.0-rc0
Reference:
https://security-tracker.debian.org/tracker/CVE-2021-3947
Dunfell utilizes qemu v4.2.0, Hence whitelisting the CVE.
--- meta/recipes-devtools/qemu/qemu.inc | 3 +++ 1 file changed, 3 insertions(+)
meta/recipes-devtools/qemu/qemu.inc +3 -0
@@ -167,6 +167,9 @@ CVE_CHECK_WHITELIST += "CVE-2020-27661" # this bug related to windows specific. CVE_CHECK_WHITELIST += "CVE-2023-0664" +# the issue introduced in v6.0.0-rc0 +CVE_CHECK_WHITELIST += "CVE-2021-3947" + COMPATIBLE_HOST_mipsarchn32 = "null" COMPATIBLE_HOST_mipsarchn64 = "null"
Signature · 1 line
2.33.0
Rather than whitelist, the upstream database should be corrected.
Please send an email to [email protected] explaining why the database entry is incorrect, providing supporting links.
It is always best to correct the database in cases like this.
Steve
Quoted 39 lines · poojitha adireddy via lists.openembedded.org
Reason:
CVE-2021-3947, issue introduced in v6.0.0-rc0
Reference:
https://security-tracker.debian.org/tracker/CVE-2021-3947Dunfell utilizes qemu v4.2.0, Hence whitelisting the CVE.
Signed-off-by poojitha adireddy <[email protected]>--- meta/recipes-devtools/qemu/qemu.inc | 3 +++ 1 file changed, 3 insertions(+)meta/recipes-devtools/qemu/qemu.inc +3
-1@@ -167,6 +167,9 @@ CVE_CHECK_WHITELIST += "CVE-2020-27661" # this bug related to windows specific. CVE_CHECK_WHITELIST += "CVE-2023-0664" +# the issue introduced in v6.0.0-rc0 +CVE_CHECK_WHITELIST += "CVE-2021-3947" + COMPATIBLE_HOST_mipsarchn32 = "null" COMPATIBLE_HOST_mipsarchn64 = "null" --2.33.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#190487): https://lists.openembedded.org/g/openembedded-core/message/190487
Mute This Topic: https://lists.openembedded.org/mt/102579083/3620601
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-