CVE-2024-9676: Podman: buildah: cri-o: symlink traversal vulnerability in the containers/storage library can cause denial of service (dos)

Published Oct 9, 2024
·
Updated

A symlink traversal vulnerability in the containers/storage library can cause Podman, Buildah, and CRI-O to hang and potentially be DoSed via OOM kill when running a malicious image using an automatically assigned user namespace (--userns=auto in Podman and Buildah). The containers/storage library will read /etc/passwd inside the container, but does not properly validate if that file is a symlink, which can be used to cause the library to read an arbitrary file on the host. This file is only read, and if it does not properly parse as a copy of /etc/passwd it will cause an error (there is a small risk of information disclosure via the error message here as elements of the file that failed to parse can be included, but this is only as the user running Podman/Buildah/CRI-O so it wouldn't be a file they did not already have access to). The report here discovered that you can symlink /etc/passwd in the container to a FIFO on the host, causing a hang as the file cannot be completely read (or an OOM condition if the FIFO is continuously written to, which was then ready by Podman). This hang could occur in a critical section in the c/storage library, blocking other processes from creating containers, but could be easily solved via a SIGKILL of the affected process. The ability to potentially crash the CRI-O service via OOM kill could be more relevant, though the attacker would have to know the path of a FIFO that is regularly being written to on the host in order to do this.

Other sources

A vulnerability was found in Podman, Buildah, and CRI-O. A symlink traversal vulnerability in the containers/storage library can cause Podman, Buildah, and CRI-O to hang and result in a denial of service via OOM kill when running a malicious image using an automatically assigned user namespace (--userns=auto in Podman and Buildah). The containers/storage library will read /etc/passwd inside the container, but does not properly validate if that file is a symlink, which can be used to cause the library to read an arbitrary file on the host.

— MITRE

Podman: buildah: cri-o: symlink traversal vulnerability in the containers/storage library can cause denial of service (dos)

— Microsoft

Affected Software

56 affected componentsFixes available
redhat OpenShift Container Platform=4.12
redhat OpenShift Container Platform=4.13
redhat OpenShift Container Platform=4.14
redhat OpenShift Container Platform=4.15
redhat OpenShift Container Platform=4.16
redhat OpenShift Container Platform=4.17
redhat Openshift Container Platform For Arm64=4.12
redhat Openshift Container Platform For Arm64=4.13
redhat Openshift Container Platform For Arm64=4.14
redhat Openshift Container Platform For Arm64=4.15
redhat Openshift Container Platform For Arm64=4.16
redhat Openshift Container Platform For Ibm Z=4.12
redhat Openshift Container Platform For Ibm Z=4.13
redhat Openshift Container Platform For Ibm Z=4.14
redhat Openshift Container Platform For Ibm Z=4.15
redhat Openshift Container Platform For Ibm Z=4.16
redhat Openshift Container Platform For Linuxone=4.12
redhat Openshift Container Platform For Linuxone=4.13
redhat Openshift Container Platform For Linuxone=4.14
redhat Openshift Container Platform For Linuxone=4.15
redhat Openshift Container Platform For Linuxone=4.16
redhat Openshift Container Platform For Power=4.12
redhat Openshift Container Platform For Power=4.13
redhat Openshift Container Platform For Power=4.14
redhat Openshift Container Platform For Power=4.15
redhat Openshift Container Platform For Power=4.16
redhat Enterprise Linux=9.0
redhat Enterprise Linux Eus=9.4
redhat Enterprise Linux For Arm 64=9.0_aarch64
redhat Enterprise Linux For Arm 64 Eus=9.4_aarch64
redhat Enterprise Linux For Ibm Z Systems=9.0_s390x
redhat Enterprise Linux For Ibm Z Systems Eus=9.4_s390x
redhat Enterprise Linux For Power Little Endian=9.0_ppc64le
redhat Enterprise Linux For Power Little Endian Eus=9.4_ppc64le
redhat Enterprise Linux Server Aus=9.4
redhat Enterprise Linux Server For Power Little Endian Update Services For Sap Solutions=9.4_ppc64le
debian/golang-github-containers-storage*
debian/golang-github-containers-storage<1.55.1+ds1-1
1.55.1+ds1-1
debian/golang-github-containers-storage<1.55.1+ds1-1
1.55.1+ds1-1
debian/golang-github-containers-storage<=1.43.0+ds1-8
1.57.2+ds1-11.64.0-1
All of the following
azurelinux/cri-o<1.22.3-14
1.22.3-14
Microsoft CBL-Mariner=2.0
All of the following
azurelinux/skopeo<1.14.4-3
1.14.4-3
Microsoft Azure Linux=3.0
All of the following
azurelinux/skopeo<1.14.2-9
1.14.2-9
Microsoft CBL-Mariner=2.0
alpine/buildah<1.37.5-r0
1.37.5-r0
alpine/buildah<1.37.5-r0
1.37.5-r0
alpine/buildah<1.37.5-r0
1.37.5-r0
alpine/buildah<1.37.5-r0
1.37.5-r0
alpine/buildah<1.37.5-r0
1.37.5-r0
alpine/podman<5.2.5-r0
5.2.5-r0
alpine/podman<5.2.5-r0
5.2.5-r0
alpine/podman<5.2.5-r0
5.2.5-r0
alpine/podman<5.2.5-r0
5.2.5-r0
alpine/podman<5.2.5-r0
5.2.5-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/golang-github-containers-storage to a version that resolves this vulnerability.

    Fixed in 1.55.1+ds1-1
  2. Upgrade

    Upgrade debian/golang-github-containers-storage to a version that resolves this vulnerability.

    Fixed in 1.57.2+ds1-1Fixed in 1.64.0-1
  3. Upgrade

    Upgrade azurelinux/cri-o to a version that resolves this vulnerability.

    Fixed in 1.22.3-14
  4. Upgrade

    Upgrade azurelinux/skopeo to a version that resolves this vulnerability.

    Fixed in 1.14.4-3
  5. Upgrade

    Upgrade azurelinux/skopeo to a version that resolves this vulnerability.

    Fixed in 1.14.2-9
  6. Upgrade

    Upgrade alpine/buildah to a version that resolves this vulnerability.

    Fixed in 1.37.5-r0
  7. Upgrade

    Upgrade alpine/podman to a version that resolves this vulnerability.

    Fixed in 5.2.5-r0

Event History

Oct 9, 2024
Data Sourced
via Red Hat·03:04 AM
DescriptionSeverityAffected Software
Oct 15, 2024
CVE Published
via MITRE·03:27 PM
Data Sourced
via MITRE·03:27 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:15 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·04:15 PM
Affected Software
Nov 14, 2024
Data Sourced
via Microsoft·08:00 AM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-9676?

CVE-2024-9676 is considered a high severity vulnerability due to its potential to hang applications and cause denial of service.

2

How do I fix CVE-2024-9676?

To fix CVE-2024-9676, update your OpenShift Container Platform installation to the latest version that addresses this vulnerability.

3

What software is affected by CVE-2024-9676?

CVE-2024-9676 affects multiple versions of Red Hat OpenShift Container Platform from 4.12 to 4.17 as well as related platforms for ARM and IBM architectures.

4

What types of attacks can exploit CVE-2024-9676?

CVE-2024-9676 can be exploited through malicious container images that cause resource exhaustion and application hangs.

5

Is there a specific configuration that increases the risk of CVE-2024-9676?

Yes, the use of the automatically assigned user namespace option ('--userns=auto') in Podman and Buildah increases the risk of CVE-2024-9676.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203