Описание
ELSA-2025-22011: buildah security update (IMPORTANT)
[1.41.6-1.0.1]
- Drop nmap-ncat requirement and skip ignore-socket test case [Orabug: 34117178]
[2:1.41.6-1]
- update to the latest content of https://github.com/containers/buildah/tree/release-1.41 (https://github.com/containers/buildah/commit/2ece502)
- fixes '[Minor Incident] CVE-2025-52881 buildah: container escape and denial of service due to arbitrary write gadgets and procfs write redirects [rhel-9.7.z]'
- Resolves: RHEL-126925
[2:1.41.4-4]
- rebuild for CVE-2025-58183
- Resolves: RHEL-125680
[2:1.41.4-3]
- fix the TMT tests
- Related: RHEL-115166
[2:1.41.4-2]
- rebuild as last build was built in the wrong tag
- Related: RHEL-115166
[2:1.41.4-1]
- update to the latest content of https://github.com/containers/buildah/tree/release-1.41 (https://github.com/containers/buildah/commit/ee5b574)
- fixes 'buildah: create parent directories of mount targets with mode 0755 - [RHEL-9.7] 0day'
- Resolves: RHEL-115166
Обновленные пакеты
Oracle Linux 9
Oracle Linux aarch64
buildah
1.41.6-1.0.1.el9_7
buildah-tests
1.41.6-1.0.1.el9_7
Oracle Linux x86_64
buildah
1.41.6-1.0.1.el9_7
buildah-tests
1.41.6-1.0.1.el9_7
Связанные CVE
Связанные уязвимости
tar.Reader does not set a maximum size on the number of sparse region data blocks in GNU tar pax 1.0 sparse files. A maliciously-crafted archive containing a large number of sparse regions can cause a Reader to read an unbounded amount of data from the archive into memory. When reading from a compressed source, a small compressed input can result in large allocations.
tar.Reader does not set a maximum size on the number of sparse region data blocks in GNU tar pax 1.0 sparse files. A maliciously-crafted archive containing a large number of sparse regions can cause a Reader to read an unbounded amount of data from the archive into memory. When reading from a compressed source, a small compressed input can result in large allocations.
Unbounded allocation when parsing GNU sparse map in archive/tar
tar.Reader does not set a maximum size on the number of sparse region ...
runc is a CLI tool for spawning and running containers according to the OCI specification. In versions 1.2.7, 1.3.2 and 1.4.0-rc.2, an attacker can trick runc into misdirecting writes to /proc to other procfs files through the use of a racing container with shared mounts (we have also verified this attack is possible to exploit using a standard Dockerfile with docker buildx build as that also permits triggering parallel execution of containers with custom shared mounts configured). This redirect could be through symbolic links in a tmpfs or theoretically other methods such as regular bind-mounts. While similar, the mitigation applied for the related CVE, CVE-2019-19921, was fairly limited and effectively only caused runc to verify that when LSM labels are written they are actually procfs files. This issue is fixed in versions 1.2.8, 1.3.3, and 1.4.0-rc.3.