Summary
[4.9.4-13.0.1]
- Fixes issue of podman execvp error while using podmansh [Orabug: 36073625]
- Improved saving remote build context to tarfile in Podman daemon [Orabug: 36495655]
- Add devices on container startup, not on creation
- Backport fast gzip for compression [Orabug: 36420418]
- overlay: Put should ignore ENINVAL for Unmount [Orabug: 36234694]
- Drop nmap-ncat requirement and skip ignore-socket test case [Orabug: 34117404]
[4:4.9.4-13]
- update to the latest content of https://github.com/containers/podman/tree/v4.9-rhel
(https://github.com/containers/podman/commit/6cf9920)
- Resolves: RHEL-60964
[4:4.9.4-12]
- rebuild to address CVE-2024-34155 CVE-2024-34156 CVE-2024-34158
- Resolves: RHEL-57980 RHEL-57950 RHEL-58203
[4:4.9.4-11]
- update to the latest content of https://github.com/containers/podman/tree/v4.9-rhel
(https://github.com/containers/podman/commit/e3221b5)
- Resolves: RHEL-56327 RHEL-50231
Fixed packages 5
| Release | Package | Fixed in |
|---|---|---|
| Oracle Linux · 9 | podman | 4:4.9.4-13.0.1.el9_4 |
| Oracle Linux · 9 | podman-docker | 4:4.9.4-13.0.1.el9_4 |
| Oracle Linux · 9 | podman-plugins | 4:4.9.4-13.0.1.el9_4 |
| Oracle Linux · 9 | podman-remote | 4:4.9.4-13.0.1.el9_4 |
| Oracle Linux · 9 | podman-tests | 4:4.9.4-13.0.1.el9_4 |
Vulnerabilities 4
-
High 7.5
Stack exhaustion in Decoder.Decode in encoding/gob
Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion. This is a follow-up to CVE-2022-30635.
-
High 7.5
Stack exhaustion in Parse in go/build/constraint
Calling Parse on a "// +build" build tag line with deeply nested expressions can cause a panic due to stack exhaustion.
-
Medium 5.4
Podman: buildah: cri-o: fips crypto-policy directory mounting issue in containers/common go library
A flaw was found in Go. When FIPS mode is enabled on a system, container runtimes may incorrectly handle certain file paths due to improper validation in the containers/common Go library. This flaw allows an attacker to exploit symbolic links and trick the sy…
-
Medium 4.3
Stack exhaustion in all Parse functions in go/parser
Calling any of the Parse functions on Go source code which contains deeply nested literals can cause a panic due to stack exhaustion.