Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Bhabu Bindu <bindudaniel1996@gmail.com>
To: openembedded-core@lists.openembedded.org, virendrak@kpit.com
Cc: akash.hadke@kpit.com
Subject: [OE-core][dunfell][PATCH] git: Whitelist CVE-2022-41953
Date: Mon, 13 Feb 2023 15:31:04 +0530	[thread overview]
Message-ID: <20230213100104.22808-1-bindudaniel1996@gmail.com> (raw)

From: Virendra Thakur <virendrak@kpit.com>

Whitelist CVE-2022-41953 as its specific to Git-for-Windows

Link: https://github.com/git-for-windows/git/security/advisories/GHSA-v4px-mx59-w99c

Upstream-Status: Pending

Issue: MGUBSYS-6605

Change-Id: Id9dde20c1c1b8244a7dc11e3eae0927d1604e7fd
Signed-off-by: Virendra Thakur <virendrak@kpit.com>
---
 meta/recipes-devtools/git/git.inc | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-devtools/git/git.inc b/meta/recipes-devtools/git/git.inc
index b5d0004712..9cc4092e17 100644
--- a/meta/recipes-devtools/git/git.inc
+++ b/meta/recipes-devtools/git/git.inc
@@ -24,6 +24,9 @@ CVE_PRODUCT = "git-scm:git"
 # we don't see this as a major issue for our general users/usecases.
 CVE_CHECK_WHITELIST += "CVE-2022-24975"
 
+# This is specific to Git-for-Windows
+CVE_CHECK_WHITELIST += "CVE-2022-41953"
+
 PACKAGECONFIG ??= ""
 PACKAGECONFIG[cvsserver] = ""
 PACKAGECONFIG[svn] = ""
-- 
2.17.1



             reply	other threads:[~2023-02-13 10:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13 10:01 Bhabu Bindu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-02-20  5:58 [OE-core][dunfell][PATCH] git: Whitelist CVE-2022-41953 Bhabu Bindu

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=20230213100104.22808-1-bindudaniel1996@gmail.com \
    --to=bindudaniel1996@gmail.com \
    --cc=akash.hadke@kpit.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=virendrak@kpit.com \
    /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