All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Anuj Mittal" <anuj.mittal@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [hardknott][PATCH 2/4] tar: ignore node-tar CVEs
Date: Wed, 22 Sep 2021 01:03:10 +0800	[thread overview]
Message-ID: <a07d4c12ca1b7f5ef233fe3885339cdf5291afb0.1632216051.git.anuj.mittal@intel.com> (raw)
In-Reply-To: <cover.1632216051.git.anuj.mittal@intel.com>

From: Armin Kuster <akuster808@gmail.com>

These three CVEs are specific to the Node package node-tar.

exclude: CVE-2021-37701 CVE-2021-37712 CVE-2021-37713

Signed-off-by: Armin Kuster <akuster808@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit 9f9317a02d73c1e5aea026683a037e52c996c7bb)
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
---
 meta/recipes-extended/tar/tar_1.34.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-extended/tar/tar_1.34.bb b/meta/recipes-extended/tar/tar_1.34.bb
index 66c11cbfea..f41e5b33d4 100644
--- a/meta/recipes-extended/tar/tar_1.34.bb
+++ b/meta/recipes-extended/tar/tar_1.34.bb
@@ -64,3 +64,4 @@ BBCLASSEXTEND = "native nativesdk"
 
 # These are both specific to the NPM package node-tar
 CVE_CHECK_WHITELIST += "CVE-2021-32803 CVE-2021-32804"
+CVE_CHECK_WHITELIST += "CVE-2021-37701 CVE-2021-37712 CVE-2021-37713"
-- 
2.31.1


  parent reply	other threads:[~2021-09-21 17:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-21 17:03 [hardknott][PATCH 0/4] Review request Anuj Mittal
2021-09-21 17:03 ` [hardknott][PATCH 1/4] sstate: Avoid problems with recipes using SRCPV when fetching sstate Anuj Mittal
2021-09-21 17:03 ` Anuj Mittal [this message]
2021-09-21 17:03 ` [hardknott][PATCH 3/4] externalsrc: Work with reproducible_build Anuj Mittal
2021-09-21 18:48   ` [OE-core] " Richard Purdie
2021-09-22  1:23     ` Anuj Mittal
2021-09-21 17:03 ` [hardknott][PATCH 4/4] ffmpeg: fix CVE-2021-38114 Anuj Mittal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a07d4c12ca1b7f5ef233fe3885339cdf5291afb0.1632216051.git.anuj.mittal@intel.com \
    --to=anuj.mittal@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.