From: Ninette Adhikari <ninette@thehoodiefirm.com>
To: openembedded-devel@lists.openembedded.org
Cc: Ninette Adhikari <ninette@thehoodiefirm.com>
Subject: [PATCH 1/1] dash: Update CVE-2024-21485 status
Date: Wed, 10 Apr 2024 14:57:34 +0200 [thread overview]
Message-ID: <20240410125734.41558-2-ninette@thehoodiefirm.com> (raw)
In-Reply-To: <20240410125734.41558-1-ninette@thehoodiefirm.com>
The recipe used in the meta-openembedded is a different dash package compared to the one which has the CVE issue.
Package used in meta-openembedded: https://git.kernel.org/pub/scm/utils/dash/dash.git
Package with CVE issue: https://github.com/plotly/dash
No action required. This issue can be removed from the CVE list.
Signed-off-by: Ninette Adhikari <ninette@thehoodiefirm.com>
---
meta-oe/recipes-shells/dash/dash_0.5.12.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta-oe/recipes-shells/dash/dash_0.5.12.bb b/meta-oe/recipes-shells/dash/dash_0.5.12.bb
index 947ef702d..ad3c75e97 100644
--- a/meta-oe/recipes-shells/dash/dash_0.5.12.bb
+++ b/meta-oe/recipes-shells/dash/dash_0.5.12.bb
@@ -10,6 +10,8 @@ inherit autotools update-alternatives
SRC_URI = "http://gondor.apana.org.au/~herbert/${BPN}/files/${BP}.tar.gz"
SRC_URI[sha256sum] = "6a474ac46e8b0b32916c4c60df694c82058d3297d8b385b74508030ca4a8f28a"
+CVE_STATUS[CVE-2024-21485] = "cpe-incorrect: The recipe used in the meta-openembedded is a different dash package compared to the one which has the CVE issue."
+
EXTRA_OECONF += "--bindir=${base_bindir}"
ALTERNATIVE:${PN} = "sh"
--
2.44.0
prev parent reply other threads:[~2024-04-10 12:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 12:57 [PATCH 0/1] dash: Update CVE-2024-21485 status Ninette Adhikari
2024-04-10 12:57 ` Ninette Adhikari [this message]
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=20240410125734.41558-2-ninette@thehoodiefirm.com \
--to=ninette@thehoodiefirm.com \
--cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).