From: Peter Marko <peter.marko@siemens.com>
To: meta-virtualization@lists.yoctoproject.org
Cc: Peter Marko <peter.marko@siemens.com>
Subject: [meta-virtualization][PATCH] podman: ignore CVE-2022-2989 and CVE-2023-0778
Date: Sat, 29 Jul 2023 23:24:28 +0200 [thread overview]
Message-ID: <20230729212428.1528245-1-peter.marko@siemens.com> (raw)
From: Peter Marko <peter.marko@siemens.com>
NVD shows only redhat links and does not mention fixed-in release
se these CVEs will show-up in reports indefinitely.
They are already fixed in current version, so ignore them.
CVE-2022-2989
* https://github.com/advisories/GHSA-4wjj-jwc9-2x96
* https://github.com/containers/podman/pull/15618
* commit d82a41687e614d9ac8b2d169dee47fe226835e4c Add container GID to additional groups
CVE-2023-0778
* https://github.com/advisories/GHSA-qwqv-rqgf-8qh8
* https://github.com/containers/podman/pull/17528
* commit 6ca857feb07a5fdc96fd947afef03916291673d8 volume,container: chroot to source before exporting content
Signed-off-by: Peter Marko <peter.marko@siemens.com>
---
recipes-containers/podman/podman_git.bb | 3 +++
1 file changed, 3 insertions(+)
diff --git a/recipes-containers/podman/podman_git.bb b/recipes-containers/podman/podman_git.bb
index 145b46f..9060e85 100644
--- a/recipes-containers/podman/podman_git.bb
+++ b/recipes-containers/podman/podman_git.bb
@@ -34,6 +34,9 @@ S = "${WORKDIR}/git"
PV = "4.6.0-rc1+git${SRCPV}"
+CVE_STATUS[CVE-2022-2989] = "fixed-version: fixed since v4.3.0"
+CVE_STATUS[CVE-2023-0778] = "fixed-version: fixed since v4.5.0"
+
PACKAGES =+ "${PN}-contrib"
PODMAN_PKG = "github.com/containers/libpod"
--
2.30.2
next reply other threads:[~2023-07-29 21:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-29 21:24 Peter Marko [this message]
2023-08-01 18:43 ` [meta-virtualization][PATCH] podman: ignore CVE-2022-2989 and CVE-2023-0778 Bruce Ashfield
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=20230729212428.1528245-1-peter.marko@siemens.com \
--to=peter.marko@siemens.com \
--cc=meta-virtualization@lists.yoctoproject.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).