NVD / CVE Program· CNA redhat

CVE-2024-3056: Podman: kernel: containers in shared ipc namespace are vulnerable to denial of service attack

Noroxi assessment

Priority: Monitor (action score 30/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.54% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
According to the record, no fixed version is available yet.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

A flaw was found in Podman. This issue may allow an attacker to create a specially crafted container that, when configured to share the same IPC with at least one other container, can create a large number of IPC resources in /dev/shm. The malicious container will continue to exhaust resources until it is out-of-memory (OOM) killed. While the malicious container's cgroup will be removed, the IPC resources it created are not. Those resources are tied to the IPC namespace that will not be removed until all containers using it are stopped, and one non-malicious container is holding the namespace open. The malicious container is restarted, either automatically or by attacker control, repeating the process and increasing the amount of memory consumed. With a container configured to restart always, such as `podman run --restart=always`, this can result in a memory-based denial of service of the system.

HighCVSS 7.7 · v3.1—No exploit No fix recorded

Denial of service

Published: Aug 2, 2024
Updated: Oct 29, 2026
EPSS: 0.5% · 45th percentile
CWE: CWE-400

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.7 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.5%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · redhat: 7.7; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
podman project	podman	cpe:2.3:a:podman_project:podman
redhat	openshift container platform	cpe:2.3:a:redhat:openshift_container_platform
redhat	enterprise linux	cpe:2.3:o:redhat:enterprise_linux
fedoraproject	fedora	cpe:2.3:o:fedoraproject:fedora

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

fedoraproject fedora40
podman project podmanup to 5.2.0 inclusive
redhat enterprise linux8.0
redhat enterprise linux9.0
redhat openshift container platform4.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

github.com/containers/podman podman
- 5.0.0affected
Red Hat Red Hat Enterprise Linux 10
- all versionsaffected
Red Hat Red Hat Enterprise Linux 7
- all versionsunknown
- all versionsunknown
- all versionsunknown
Red Hat Red Hat Enterprise Linux 8
- all versionsunknown
- all versionsunknown
- all versionsaffected
- all versionsaffected
Red Hat Red Hat Enterprise Linux 9
- all versionsaffected
- all versionsunknown
Red Hat Red Hat OpenShift Container Platform 3.11
- all versionsunknown
Red Hat Red Hat OpenShift Container Platform 4
- all versionsunknown

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Go	github.com/containers/podman	from 0	—
Go	github.com/containers/podman	up to and including 5.2.0	—
Go	github.com/containers/podman/v2	from 0	—
Go	github.com/containers/podman/v2	up to and including 5.2.0	—
Go	github.com/containers/podman/v3	from 0	—
Go	github.com/containers/podman/v3	up to and including 5.2.0	—
Go	github.com/containers/podman/v4	from 0	—
Go	github.com/containers/podman/v4	up to and including 5.2.0	—
Go	github.com/containers/podman/v5	from 0	—
Go	github.com/containers/podman/v5	up to and including 5.2.0	—

Same product

podman project: all records

Other highest-scoring records for the same primary product.

CVE-2022-1227A privilege escalation flaw was found in Podman.
36Monitor
CVE-2026-57231Podman: Malformed Image can trick podman run into leaking host environment variables into the container
30Monitor
CVE-2022-27649A flaw was found in Podman, where containers were started incorrectly with non-empty default permissions.
30Monitor

Published before and after this one in the same product

← EarlierCVE-2022-4123Dec 8, 2022 · A flaw was found in Buildah.
13Monitor
← EarlierCVE-2023-0778Mar 27, 2023 · A Time-of-check Time-of-use (TOCTOU) flaw was found in podman.
27Monitor
Later →CVE-2026-33414Apr 14, 2026 · PowerShell Command Injection in Podman HyperV Machine
16Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-24-1154 · Aug 5, 2024(RedHat Podman Güvenlik Bildirimi)

All national notices →

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
A user must open a link or visit a page.
Special conditions such as timing or configuration are required.

If successful

Confidentiality: high · data can be read
Integrity: none
Availability: high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector: Network
Attack complexity: High
Privileges required: Low
User interaction: Required
Scope: Changed
Confidentiality impact: High
Integrity impact: None
Availability impact: High

Weakness class (CWE)

CWE-400 · Uncontrolled Resource Consumption

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:H

nvd-secondary

Root cause

Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.

The bug in code

The whole CWE-400 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1function expand(node) {
2  return node.children.map(expand);
3}

Fixed

1const MAX_DEPTH = 32;
2function expand(node, depth = 0) {
3  if (depth > MAX_DEPTH) throw new Error("too deep");
4  return node.children.map((c) => expand(c, depth + 1));
5}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Endpoint Denial of ServiceT1499

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

access.redhat.com/security/cve/CVE-2024-3056

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records