From: Ninette Adhikari <ninette@thehoodiefirm.com>
To: openembedded-devel@lists.openembedded.org
Cc: engineering@neighbourhood.ie, Peter.Marko@siemens.com,
Ninette Adhikari <ninette@thehoodiefirm.com>
Subject: [PATCH v2] mpd: Update status for CVE-2020-7465 and CVE-2020-7466
Date: Mon, 29 Apr 2024 17:04:50 +0200 [thread overview]
Message-ID: <20240429150450.13931-1-ninette@thehoodiefirm.com> (raw)
In-Reply-To: <AS1PR10MB5697CBD433A5B23B6FA7F0F3FD1B2@AS1PR10MB5697.EURPRD10.PROD.OUTLOOK.COM>
The recipe used in the `meta-openembedded` is a different mpd package compared to the one which has the CVE issue.
Package used in `meta-embedded`: http://www.musicpd.org
Package with CVE issue: https://sourceforge.net/projects/mpd/
No action required.
Signed-off-by: Ninette Adhikari <ninette@thehoodiefirm.com>
---
meta-multimedia/recipes-multimedia/musicpd/mpd_0.23.14.bb | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta-multimedia/recipes-multimedia/musicpd/mpd_0.23.14.bb b/meta-multimedia/recipes-multimedia/musicpd/mpd_0.23.14.bb
index a762fc832..f30fffebe 100644
--- a/meta-multimedia/recipes-multimedia/musicpd/mpd_0.23.14.bb
+++ b/meta-multimedia/recipes-multimedia/musicpd/mpd_0.23.14.bb
@@ -100,3 +100,6 @@ USERADD_PARAM:${PN} = " \
--home ${localstatedir}/lib/mpd \
--groups audio \
--user-group mpd"
+
+CVE_STATUS[CVE-2020-7465] = "cpe-incorrect: The recipe used in the meta-openembedded is a different mpd package compared to the one which has the CVE issue."
+CVE_STATUS[CVE-2020-7466] = "cpe-incorrect: The recipe used in the meta-openembedded is a different mpd package compared to the one which has the CVE issue."
--
2.44.0
prev parent reply other threads:[~2024-04-29 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 11:07 [PATCH 0/1] mpd: Update status for CVE-2020-7465 and CVE-2020-7466 Ninette Adhikari
2024-04-29 11:07 ` [PATCH 1/1] " Ninette Adhikari
2024-04-29 11:56 ` [oe] " Marko, Peter
2024-04-29 15:04 ` 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=20240429150450.13931-1-ninette@thehoodiefirm.com \
--to=ninette@thehoodiefirm.com \
--cc=Peter.Marko@siemens.com \
--cc=engineering@neighbourhood.ie \
--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).