Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: sam.voss@gmail.com
To: buildroot@buildroot.org
Cc: Sam Voss <sam.voss@gmail.com>
Subject: [Buildroot] [PATCH] package/ripgrep: ignore CVE-2021-3013 as Windows only
Date: Wed, 29 Sep 2021 22:52:49 -0500	[thread overview]
Message-ID: <20210930035250.23687-1-sam.voss@gmail.com> (raw)

From: Sam Voss <sam.voss@gmail.com>

CVE-2021-3013 does not impact any buildroot versions of ripgrep as it is
a Windows-only exploit targeting ripgrep versions earlier than 13. It
can be safely ignored on our LTS branches.

Signed-off-by: Sam Voss <sam.voss@gmail.com>

---

Note: Please apply this patch to:

  * 2021.02.x
  * 2021.05.x
  * 2021.08.x

Master currently has version 13, which does not report this CVE.
---
 package/ripgrep/ripgrep.mk | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/package/ripgrep/ripgrep.mk b/package/ripgrep/ripgrep.mk
index 450bb020e3..8d0185595d 100644
--- a/package/ripgrep/ripgrep.mk
+++ b/package/ripgrep/ripgrep.mk
@@ -10,6 +10,9 @@ RIPGREP_LICENSE = MIT
 RIPGREP_LICENSE_FILES = LICENSE-MIT
 RIPGREP_CPE_ID_VENDOR = ripgrep_project
 
+# CVE only impacts ripgrep on Windows
+RIPGREP_IGNORE_CVES += CVE-2021-3013
+
 RIPGREP_DEPENDENCIES = host-rustc
 RIPGREP_CARGO_ENV = CARGO_HOME=$(HOST_DIR)/share/cargo \
 	__CARGO_TEST_CHANNEL_OVERRIDE_DO_NOT_USE_THIS="nightly" \
-- 
2.33.0

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2021-09-30  3:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-30  3:52 sam.voss [this message]
2021-10-03 20:19 ` [Buildroot] [PATCH] package/ripgrep: ignore CVE-2021-3013 as Windows only Yann E. MORIN
2021-10-06 15:22 ` Peter Korsgaard

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=20210930035250.23687-1-sam.voss@gmail.com \
    --to=sam.voss@gmail.com \
    --cc=buildroot@buildroot.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox