CVE-2024-9676

6.5 MEDIUM

📋 TL;DR

A symlink traversal vulnerability in the containers/storage library used by Podman, Buildah, and CRI-O allows malicious container images to cause denial of service via OOM kill. Attackers can exploit this by creating a symlink from /etc/passwd inside the container to an arbitrary host file, causing the system to hang and potentially crash. This affects systems running these container tools with automatically assigned user namespaces.

💻 Affected Systems

Products:
  • Podman
  • Buildah
  • CRI-O
Versions: Versions using vulnerable containers/storage library (specific versions in Red Hat advisories)
Operating Systems: Linux distributions with affected container tools
Default Config Vulnerable: ✅ No
Notes: Only vulnerable when using automatically assigned user namespaces (--userns=auto flag in Podman/Buildah). Default configurations may not be affected.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system denial of service via OOM kill, potentially crashing the host system and disrupting all containerized workloads.

🟠

Likely Case

Container runtime hangs and becomes unresponsive, requiring manual intervention to restart services and affected containers.

🟢

If Mitigated

Minimal impact with proper patching and security controls; isolated container failures without host system compromise.

🌐 Internet-Facing: MEDIUM - Requires pulling and running a malicious container image, which could happen through compromised registries or supply chain attacks.
🏢 Internal Only: MEDIUM - Internal users with container deployment privileges could exploit this, but requires specific configuration (--userns=auto).

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Requires ability to create and run malicious container images with specific symlink configurations. Not trivial but achievable by skilled attackers.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check specific Red Hat advisories for version numbers

Vendor Advisory: https://access.redhat.com/errata/RHSA-2024:10289

Restart Required: Yes

Instructions:

1. Update containers/storage library to patched version. 2. Update affected container tools (Podman, Buildah, CRI-O) to latest versions. 3. Restart container services and affected containers.

🔧 Temporary Workarounds

Disable automatic user namespaces

linux

Avoid using --userns=auto flag when running containers

podman run --userns=keep-id ...
podman run --userns=host ...

Use podman machine for rootless containers

linux

Run containers in isolated VM environments

podman machine init
podman machine start

🧯 If You Can't Patch

  • Avoid pulling container images from untrusted sources
  • Implement strict image signing and verification policies

🔍 How to Verify

Check if Vulnerable:

Check if using --userns=auto flag and verify containers/storage library version against patched versions in Red Hat advisories

Check Version:

rpm -q containers-storage or podman version

Verify Fix Applied:

Verify containers/storage library is updated to patched version and test container runs without hanging

📡 Detection & Monitoring

Log Indicators:

  • Container runtime hangs
  • OOM kill events in system logs
  • High memory usage by container processes

Network Indicators:

  • Unusual container image pulls from untrusted sources

SIEM Query:

search 'OOM kill' AND 'container' OR 'podman' OR 'crio' in system logs

🔗 References

📤 Share & Export