# CVE-2024-9676: Path traversal in OpenShift Developer Tools and Services > A symlink traversal flaw in containers/storage allows malicious images to cause denial of service and read arbitrary host files when using auto user namespaces. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 15 Oct 2024 - **Updated:** 24 Apr 2026 - **Also known as:** AZL-50598, AZL-50601, AZL-50609, AZL-50612, AZL-50614, AZL-50620, AZL-50623, AZL-50629, BELL-CVE-2024-9676, CLEANSTART-2024-KQ32668, CLSA-2025-1762180294, DEBIAN-CVE-2024-9676, GHSA-wq2p-5pc6-wpgf, OESA-2026-3445, OESA-2026-3446, OESA-2026-3447, OESA-2026-3448, RHSA-2024:8437, SUSE-SU-2024:3753-1, SUSE-SU-2024:3754-1, SUSE-SU-2025:20085-1, UBUNTU-CVE-2024-9676, openSUSE-SU-2024:14418-1, openSUSE-SU-2024:14420-1, openSUSE-SU-2024:14562-1 ## What is CVE-2024-9676? CVE-2024-9676 is a medium-severity path traversal vulnerability in Redhat Enterprise Linux, published on 15 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description 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. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2024-9676? It affects 15 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `cri-o` | Red Hat:openshift:4.17::el8 | All versions | 0:1.30.6-6.rhaos4.17.git6ac6e96.el8 | | `cri-o-debuginfo` | Red Hat:openshift:4.17::el8 | All versions | 0:1.30.6-6.rhaos4.17.git6ac6e96.el8 | | `cri-o-debugsource` | Red Hat:openshift:4.17::el8 | All versions | 0:1.30.6-6.rhaos4.17.git6ac6e96.el8 | | `cri-o` | Red Hat:openshift:4.17::el9 | All versions | 0:1.30.6-6.rhaos4.17.git6ac6e96.el9 | | `cri-o-debuginfo` | Red Hat:openshift:4.17::el9 | All versions | 0:1.30.6-6.rhaos4.17.git6ac6e96.el9 | | `cri-o-debugsource` | Red Hat:openshift:4.17::el9 | All versions | 0:1.30.6-6.rhaos4.17.git6ac6e96.el9 | | `podman` | SUSE:Linux Enterprise Micro 5.5 | All versions | 4.9.5-150500.3.28.1 | | `buildah` | SUSE:Linux Enterprise Module for Containers 15 SP5 | All versions | 1.35.4-150500.3.19.1 | | `podman` | SUSE:Linux Enterprise Module for Containers 15 SP5 | All versions | 4.9.5-150500.3.28.1 | | `buildah` | SUSE:Linux Enterprise Module for Containers 15 SP6 | All versions | 1.35.4-150500.3.19.1 | | `podman` | SUSE:Linux Enterprise Module for Containers 15 SP6 | All versions | 4.9.5-150500.3.28.1 | | `skopeo` | SUSE:Linux Micro 6.0 | All versions | 1.14.4-2.1 | | `buildah` | openSUSE:Leap 15.5 | All versions | 1.35.4-150500.3.19.1 | | `podman` | openSUSE:Leap 15.5 | All versions | 4.9.5-150500.3.28.1 | | `buildah` | openSUSE:Leap 15.6 | All versions | 1.35.4-150500.3.19.1 | | `podman` | openSUSE:Leap 15.6 | All versions | 4.9.5-150500.3.28.1 | | `podman` | openSUSE:Leap Micro 5.5 | All versions | 4.9.5-150500.3.28.1 | | `buildah` | openSUSE:Tumbleweed | All versions | 1.37.5-1.1 | | `podman` | openSUSE:Tumbleweed | All versions | 5.2.4-3.1 | | `skopeo` | openSUSE:Tumbleweed | All versions | 1.16.1-2.1 | Products: Redhat Enterprise Linux, Redhat Enterprise Linux Eus, Redhat Enterprise Linux for Arm 64, Redhat Enterprise Linux for Arm 64 Eus, Redhat Enterprise Linux for Ibm Z Systems, Redhat Enterprise Linux for Ibm Z Systems Eus, Redhat Enterprise Linux for Power Little Endian, Redhat Enterprise Linux for Power Little Endian Eus, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server for Power Little Endian Update Services for Sap Solutions, Redhat Openshift Container Platform, Redhat Openshift Container Platform for Arm64, Redhat Openshift Container Platform for Ibm Z, Redhat Openshift Container Platform for Linuxone, Redhat Openshift Container Platform for Power. ## How do I fix CVE-2024-9676? Apply the vendor's patch. ## Is CVE-2024-9676 being exploited? There is no known exploitation of CVE-2024-9676 in the wild and no public exploit code. ## Other vulnerabilities in Redhat Enterprise Linux - [CVE-2018-14667](https://insights.sbomify.com/CVE-2018-14667/): Red Hat JBoss RichFaces Framework Expression Language Injection (critical 9.8, exploited in the wild) - [CVE-2021-20325](https://insights.sbomify.com/CVE-2021-20325/): Missing fixes for CVE-2021-40438 and CVE-2021-26691 in the versions of httpd, as shipped in Red Hat Enterprise Linux 8.5.0, causes a securit (critical 9.8) - [CVE-2018-25011](https://insights.sbomify.com/CVE-2018-25011/): Memory corruption in libwebp (critical 9.8) - [CVE-2018-25014](https://insights.sbomify.com/CVE-2018-25014/): Other in libwebp (critical 9.8) - [CVE-2014-3585](https://insights.sbomify.com/CVE-2014-3585/): Supply chain in redhat-upgrade-tool (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-9676 and fix it if it is affected. What it is: CVE-2024-9676 is a medium-severity path traversal vulnerability in Redhat Enterprise Linux, published on 15 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-9676 in the wild and no public exploit code. Affected product: Redhat Enterprise Linux. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-9676/ (Markdown: https://insights.sbomify.com/CVE-2024-9676/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-9676 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-9676 - OSV: https://osv.dev/vulnerability/CVE-2024-9676 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-9676/ Summaries are generated and may contain mistakes; the official description above is the record.