Summary
The podman tool manages pods, container images, and containers. It is part of the libpod library, which is for applications that use container pods. Container pods is a concept in Kubernetes.
Security Fix(es):
* go/parser: golang: Calling any of the Parse functions containing deeply nested literals can cause a panic/stack exhaustion (CVE-2024-34155)
* encoding/gob: golang: Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion (CVE-2024-34156)
* go/build/constraint: golang: Calling Parse on a "// +build" build tag line with deeply nested expressions can cause a panic due to stack exhaustion (CVE-2024-34158)
* Podman: Buildah: cri-o: FIPS Crypto-Policy Directory Mounting Issue in containers/common Go Library (CVE-2024-9341)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Fixed packages 5
| Release | Package | Fixed in |
|---|---|---|
| AlmaLinux · 9 | podman | 4:4.9.4-13.el9_4 |
| AlmaLinux · 9 | podman-docker | 4:4.9.4-13.el9_4 |
| AlmaLinux · 9 | podman-plugins | 4:4.9.4-13.el9_4 |
| AlmaLinux · 9 | podman-remote | 4:4.9.4-13.el9_4 |
| AlmaLinux · 9 | podman-tests | 4:4.9.4-13.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.
References
-
report
https://access.redhat.com/security/cve/CVE-2024-34155
-
report
https://access.redhat.com/security/cve/CVE-2024-34156
-
report
https://access.redhat.com/security/cve/CVE-2024-34158
-
report
https://access.redhat.com/security/cve/CVE-2024-9341
-
report
https://bugzilla.redhat.com/2310527
-
report
https://bugzilla.redhat.com/2310528
-
report
https://bugzilla.redhat.com/2310529
-
report
https://bugzilla.redhat.com/2315691
-
advisory
https://errata.almalinux.org/9/ALSA-2024-8039.html