CVE-2024-1753 — v4
HIGHCVE-2024-1753 is a high-severity (CVSS 8.6) CWE-59 vulnerability in github.com/containers/podman/v4. A fix is available for github.com/containers/podman/v4 — see the affected versions and patch details below.
Podman affected by CVE-2024-1753 container escape at build time
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-1753.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2024-1753 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/containers/podman/v4🐹github.com/containers/podman/v5Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
A flaw was found in Buildah (and subsequently Podman Build) which allows containers to mount arbitrary locations on the host filesystem into build containers. A malicious Containerfile can use a dummy image with a symbolic link to the root filesystem as a mount source and cause the mount operation to mount the host root filesystem inside the RUN step. The commands inside the RUN step will then have read-write access to the host filesystem, allowing for full container escape at build time.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/containers/podman/v4 | all versions | 4.9.4go get github.com/containers/podman/v4@v4.9.4 |
| 🐹Go | github.com/containers/podman/v5 | all versions | 5.0.1go get github.com/containers/podman/v5@v5.0.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/containers/podman/v4, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/containers/podman/v4 to 4.9.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-1753 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-1753 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-1753. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 8 | container-tools:4.0-8090020240413110917.d7b6f4b7 | RHSA-2024:2084 |
| Red Hat Enterprise Linux 8 | container-tools:rhel8-8090020240417184044.e7857ab1 | RHSA-2024:2098 |
| Red Hat Enterprise Linux 8 | container-tools:rhel8-8100020240419145834.afee755d | RHSA-2024:3254 |
| Red Hat Enterprise Linux 8.6 Extended Update Support | container-tools:rhel8-8060020240422155330.3b538bd8 | RHSA-2024:2090 |
| Red Hat Enterprise Linux 8.6 Extended Update Support | container-tools:4.0-8060020240419071711.2e213529 | RHSA-2024:2097 |
| Red Hat Enterprise Linux 8.8 Extended Update Support | container-tools:rhel8-8080020240422101606.0f77c1b7 | RHSA-2024:2077 |
| Red Hat Enterprise Linux 9 | buildah-1:1.31.5-1.el9_3 | RHSA-2024:2055 |
| Red Hat Enterprise Linux 9 | podman-4:4.9.4-3.el9_4 | RHSA-2024:2548 |
Frequently Asked Questions
Is CVE-2024-1753 in your dependencies?
O3 Security finds CVE-2024-1753 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.