dbcve.org
Openshift Container PlatformApplication · Redhat

CVE-2024-3056

HIGH · 7.7 CVSS v3.1 Published 2024-08-02
Fix available
A fix is available. Upgrade to after 5.2.0 or later.
See remediation →
81/100
Remediation priority · High
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This Podman vulnerability allows a malicious container configured to share IPC with other containers to create excessive IPC resources in /dev/shm. When the container is OOM-killed and restarted (especially with --restart=always), IPC resources are not cleaned up because the IPC namespace remains open via a non-malicious container, causing cumulative memory exhaustion and denial of service.

MitigationImplement container resource limits (--memory, --shm-size) and avoid sharing IPC namespaces between untrusted containers. Update Podman to patched version when available and monitor /dev/shm usage.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Openshift Container PlatformApplication
Affected:= 4.0
Enterprise LinuxOperating system
Affected:= 8.0= 9.0
FedoraOperating system
Affected:= 40
PodmanApplication
Affected:<= 5.2.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Podman version
    Run 'podman --version' and compare the output to the affected range: Podman <= 5.2.0
    Affected if Podman version is 5.2.0 or lower
  2. Locate containers using IPC namespace sharing
    Run 'podman ps -a --format "{{.ID}} {{.Names}} {{.IPCMode}}"' to list containers and their IPC mode configuration
    Affected if Any container shows an IPC mode other than 'private' (such as 'host' or 'container:<name>') indicating IPC namespace sharing is enabled
  3. Identify containers with automatic restart policy
    Run 'podman ps -a --format "{{.Names}} {{.RestartPolicy}}"' to find containers configured with --restart=always or similar restart policies
    Affected if Any container using --restart=always or --restart=on-failure with IPC sharing is configured
  4. Inspect /dev/shm usage and IPC objects
    Run 'ls -la /dev/shm' and check for excessive file count or size; run 'ipcs -m' to list shared memory segments
    Affected if /dev/shm shows unusually high number of files or 'ipcs -m' shows many lingering shared memory segments not tied to running containers
  5. Check for orphaned IPC namespaces
    Run 'podman ps -a' to list all containers, then run 'ls -la /proc/$(podman inspect --format '{{.State.Pid}}' <container_id>)/ns/' for each to inspect namespace entries
    Affected if Multiple IPC namespace references exist without corresponding active container processes

A system is affected if running Podman <= 5.2.0 with containers configured to share IPC namespaces and using automatic restart policies, combined with evidence of excessive /dev/shm usage or orphaned IPC resources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 5.2.0
Interim mitigation

Implement container resource limits (--memory, --shm-size) and avoid sharing IPC namespaces between untrusted containers. Update Podman to patched version when available and monitor /dev/shm usage.

Recommended fix Moderate confidence

Podman 5.2.1 or later

  1. Upgrade Podman to version 5.2.1 or later
  2. Verify the upgrade using `podman --version`
  3. Ensure containers using IPC namespaces are properly managed and monitored
  4. Consider implementing resource limits (--memory, --memory-swap) on containers as an additional mitigation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openshift Container Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-3056 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-3056 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data