From: "Mittal, Anuj" <anuj.mittal@intel.com>
To: "ankur.tyagi85@gmail.com" <ankur.tyagi85@gmail.com>,
"openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Cc: "ninette@thehoodiefirm.com" <ninette@thehoodiefirm.com>,
"raj.khem@gmail.com" <raj.khem@gmail.com>
Subject: Re: [oe][meta-oe][scarthgap][PATCH 1/4] mercurial: Update CVE status for CVE-2022-43410
Date: Thu, 30 Oct 2025 06:38:25 +0000 [thread overview]
Message-ID: <fcb5f25762c06c8566d2fcfbcd4d0c2ad4e8c28a.camel@intel.com> (raw)
In-Reply-To: <20251015063531.1573191-1-ankur.tyagi85@gmail.com>
On Wed, 2025-10-15 at 19:35 +1300, Ankur Tyagi via
lists.openembedded.org wrote:
> From: Ninette Adhikari <ninette@thehoodiefirm.com>
>
> The recipe used in the `meta-openembedded` is a different mercurial
> package compared to the one which has the CVE issue.
> Package used in `meta-embedded`: https://www.mercurial-scm.org/
> Package with CVE issue is a Jenkins plugin:
> https://plugins.jenkins.io/mercurial/
> (This is reflected in the CPE)
>
> Signed-off-by: Ninette Adhikari <ninette@thehoodiefirm.com>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> (cherry picked from commit bf84ac1c4c1a00c2aa92a09fbdfae128d055fe05)
> Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
> ---
> meta-oe/recipes-devtools/mercurial/mercurial_6.5.bb | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta-oe/recipes-devtools/mercurial/mercurial_6.5.bb
> b/meta-oe/recipes-devtools/mercurial/mercurial_6.5.bb
> index 2451a36be2..53fe0a28ae 100644
> --- a/meta-oe/recipes-devtools/mercurial/mercurial_6.5.bb
> +++ b/meta-oe/recipes-devtools/mercurial/mercurial_6.5.bb
> @@ -34,3 +34,4 @@ PACKAGES =+ "${PN}-python"
> FILES:${PN} += "${PYTHON_SITEPACKAGES_DIR} ${datadir}"
> FILES:${PN}-python = "${nonarch_libdir}/${PYTHON_DIR}"
>
> +CVE_STATUS[CVE-2022-43410] = "cpe-incorrect: The recipe used in the
> `meta-openembedded` is a different mercurial package compared to the
> one which has the CVE issue."
This shouldn't be a cpe-incorrect in that case and should use
mercurial-scm as the vendor in CVE_PRODUCT.
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#120690):
> https://lists.openembedded.org/g/openembedded-devel/message/120690
> Mute This Topic: https://lists.openembedded.org/mt/115766810/3616702
> Group Owner: openembedded-devel+owner@lists.openembedded.org
> Unsubscribe:
> https://lists.openembedded.org/g/openembedded-devel/unsub [
> anuj.mittal@intel.com]
> -=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2025-10-30 6:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 6:35 [oe][meta-oe][scarthgap][PATCH 1/4] mercurial: Update CVE status for CVE-2022-43410 Ankur Tyagi
2025-10-15 6:35 ` [oe][meta-oe][scarthgap][PATCH 2/4] libvpx: patch CVE-2024-5197 Ankur Tyagi
2025-10-15 8:44 ` Gyorgy Sarvari
2025-10-15 9:23 ` Ankur Tyagi
2025-10-15 6:35 ` [oe][meta-oe][scarthgap][PATCH 3/4] neatvnc: upgrade to 0.8.1 release Ankur Tyagi
2025-10-30 6:30 ` Mittal, Anuj
2025-10-30 8:33 ` Ankur Tyagi
2025-10-15 6:35 ` [oe][meta-oe][scarthgap][PATCH 4/4] opencv: ignore CVE-2025-53644 Ankur Tyagi
2025-10-30 6:27 ` Mittal, Anuj
2025-10-30 8:10 ` Ankur Tyagi
2025-10-30 6:38 ` Mittal, Anuj [this message]
2025-10-31 0:41 ` [oe][meta-oe][scarthgap][PATCH 1/4] mercurial: Update CVE status for CVE-2022-43410 Ankur Tyagi
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=fcb5f25762c06c8566d2fcfbcd4d0c2ad4e8c28a.camel@intel.com \
--to=anuj.mittal@intel.com \
--cc=ankur.tyagi85@gmail.com \
--cc=ninette@thehoodiefirm.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.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 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.