# CVE-2024-3727: Containers/image: digest type does not guarantee valid type > Attackers can trigger unexpected registry accesses causing resource exhaustion and local path traversal in the containers/image library. - **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 9 May 2024 - **Updated:** 29 Oct 2026 - **Also known as:** AZL-42315, AZL-42318, AZL-42319, AZL-42327, AZL-42330, AZL-42331, AZL-42340, AZL-42343, AZL-43492, AZL-43510, AZL-44565, AZL-44970, AZL-45243, BELL-CVE-2024-3727, CLEANSTART-2024-VD14033, DEBIAN-CVE-2024-3727, GHSA-6wvf-f2vw-3425, GO-2024-2842, SUSE-SU-2024:1838-1, SUSE-SU-2024:1988-1, SUSE-SU-2024:1989-1, SUSE-SU-2024:2383-1, SUSE-SU-2024:2548-1, SUSE-SU-2025:20055-1, UBUNTU-CVE-2024-3727, openSUSE-SU-2024:13951-1, openSUSE-SU-2024:13960-1, openSUSE-SU-2024:13963-1, openSUSE-SU-2024:13975-1, openSUSE-SU-2024:14019-1, openSUSE-SU-2026:11054-1, openSUSE-SU-2026:11074-1 ## What is CVE-2024-3727? CVE-2024-3727 is a high-severity path traversal vulnerability in Red Hat Multicluster Engine for Kubernetes, published on 9 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description A flaw was found in the github.com/containers/image library. This flaw allows attackers to trigger unexpected authenticated registry accesses on behalf of a victim user, causing resource exhaustion, local path traversal, and other attacks. Weakness: CWE-354 (Improper Validation of Integrity Check Value) ## Which versions are affected by CVE-2024-3727? 7 open source packages ship an affected version, including github.com/containers/image/v5 and github.com/containers/image. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/containers/image/v5` | Go | All versions | 5.29.3, 5.30.1 | | `github.com/containers/image/v5` | Go | All versions | 5.29.3 | | `github.com/containers/image/v5` | Go | All versions | 5.29.3 | | `github.com/containers/image/v5` | Go | From 5.30.0 | 5.30.1 | | `github.com/containers/image/v5` | Go | From 5.30.0 | 5.30.1 | | `github.com/containers/image` | Go | All versions | 5.30.1 | | `github.com/containers/image` | Go | All versions | 5.30.1 | | `podman` | SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | All versions | 2.1.1-150100.4.31.1 | | `skopeo` | SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | All versions | 0.1.41-150000.4.23.1 | | `containerized-data-importer` | SUSE:Linux Enterprise Micro 5.5 | All versions | 1.58.0-150500.6.15.1 | | `containerized-data-importer` | SUSE:Linux Enterprise Module for Containers 15 SP5 | All versions | 1.58.0-150500.6.15.1 | | `containerized-data-importer` | SUSE:Linux Enterprise Module for Containers 15 SP6 | All versions | 1.58.0-150600.3.3.2 | | `warewulf4` | SUSE:Linux Enterprise Module for HPC 15 SP5 | All versions | 4.5.2-150500.6.13.1 | | `warewulf4` | SUSE:Linux Enterprise Module for HPC 15 SP6 | All versions | 4.5.2-150500.6.13.1 | | `podman` | SUSE:Linux Enterprise Server 15 SP2-LTSS | All versions | 2.1.1-150100.4.31.1 | | `skopeo` | SUSE:Linux Enterprise Server 15 SP2-LTSS | All versions | 0.1.41-150000.4.23.1 | | `podman` | SUSE:Linux Enterprise Server for SAP Applications 15 SP2 | All versions | 2.1.1-150100.4.31.1 | | `skopeo` | SUSE:Linux Enterprise Server for SAP Applications 15 SP2 | All versions | 0.1.41-150000.4.23.1 | | `containerized-data-importer` | SUSE:Linux Micro 6.0 | All versions | 1.60.1-1.1 | | `containerized-data-importer` | openSUSE:Leap 15.5 | All versions | 1.58.0-150500.6.15.1 | | `warewulf4` | openSUSE:Leap 15.5 | All versions | 4.5.2-150500.6.13.1 | | `containerized-data-importer` | openSUSE:Leap 15.6 | All versions | 1.58.0-150600.3.3.2 | | `warewulf4` | openSUSE:Leap 15.6 | All versions | 4.5.2-150500.6.13.1 | | `apptainer` | openSUSE:Tumbleweed | All versions | 1.3.0-2.1 | | `containerized-data-importer-1.65` | openSUSE:Tumbleweed | All versions | 1.65.0-1.1 | | `containerized-data-importer1.65` | openSUSE:Tumbleweed | All versions | 1.65.0-1.1 | | `podman` | openSUSE:Tumbleweed | All versions | 5.0.3-1.1 | | `skopeo` | openSUSE:Tumbleweed | All versions | 1.15.1-1.1 | ## How do I fix CVE-2024-3727? Upgrade github.com/containers/image/v5 to a fixed version for your release line: 5.29.3 or 5.30.1. ## Is CVE-2024-3727 being exploited? There is no known exploitation of CVE-2024-3727 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-3727 and fix it if it is affected. What it is: CVE-2024-3727 is a high-severity path traversal vulnerability in Red Hat Multicluster Engine for Kubernetes, published on 9 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2024-3727 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/containers/image/v5 (Go): affected all versions; fixed in 5.29.3, 5.30.1 - github.com/containers/image/v5 (Go): affected all versions; fixed in 5.29.3 - github.com/containers/image/v5 (Go): affected all versions; fixed in 5.29.3 - github.com/containers/image/v5 (Go): affected from 5.30.0; fixed in 5.30.1 - github.com/containers/image/v5 (Go): affected from 5.30.0; fixed in 5.30.1 - github.com/containers/image (Go): affected all versions; fixed in 5.30.1 - github.com/containers/image (Go): affected all versions; fixed in 5.30.1 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-3727/ (Markdown: https://insights.sbomify.com/CVE-2024-3727/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-3727 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-3727 - OSV: https://osv.dev/vulnerability/CVE-2024-3727 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-3727/ Summaries are generated and may contain mistakes; the official description above is the record.