CVE-2024-11218 fix #25099
CVE-2024-11218 fix #25099
Conversation
This vendors Buildah from the top of the main branch as of January 22, 2025. This included the fixes for CVE-2024-11218. Fixes: https://issues.redhat.com/browse/RHEL-67605, https://issues.redhat.com/browse/RHEL-67607 Signed-off-by: tomsweeneyredhat <[email protected]>
TomSweeneyRedHat
added
do-not-merge/work-in-progress
openshift-ci
bot
added
release-note
and removed
do-not-merge/work-in-progress
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: TomSweeneyRedHat The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
|
Ephemeral COPR build failed. @containers/packit-build please check. |
|
@Luap99 PTAL. I tried vendoring top of tree for Buildah, but it looks like it updated c/image and c/storage to the latest release rather than their respective top of trees, but I think we might not want to do that. We may have a catch-22.... Thoughts? |
|
That is the usual go being unable to figure out how our versions work. We need containers/buildah#5932 and containers/buildah#5929 first merged in buildah |
|
I drive the vendor forward in #25130 |
This vendors Buildah from the top of the main branch as of January 22, 2025. This included the fixes for CVE-2024-11218.
Fixes: https://issues.redhat.com/browse/RHEL-67605, https://issues.redhat.com/browse/RHEL-67607
Does this PR introduce a user-facing change?