REDHAT-BUG-2270717: Medium severity Podman Podman vulnerability

Published Mar 21, 2024
·
Updated

Summary: We received a report of an attack vector on containers which share an IPC namespace (definitely Podman, but likely also applicable to Kubernetes, Docker, and other container runtimes). At least two containers are configured with a shared IPC namespace and a cgroup limiting memory. One of those containers is malicious, and contains a binary which creates a large number of IPC resources in /dev/shm, and continues doing so until it is OOM killed. The malicious container is now dead, its cgroup removed, but the IPC resources it created are not; they 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 (e.g. podman run --restart=always) this results in a memory-based denial of service of the system.

Podman Version: Version 5.0.0-dev and before

Affected Software

3 affected components
Podman Podman
Kubernetes kubernetes
Docker Docker

Event History

Mar 21, 2024
Data Sourced
via Red Hat·02:56 PM
DescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of REDHAT-BUG-2270717?

The severity of REDHAT-BUG-2270717 is significant due to the potential for unauthorized access between containers sharing an IPC namespace.

2

How do I fix REDHAT-BUG-2270717?

To fix REDHAT-BUG-2270717, avoid configuring containers with a shared IPC namespace.

3

Which container technologies are affected by REDHAT-BUG-2270717?

REDHAT-BUG-2270717 affects Podman, and potentially Kubernetes and Docker, when containers share an IPC namespace.

4

What is the attack vector described in REDHAT-BUG-2270717?

The attack vector in REDHAT-BUG-2270717 involves containers that share an IPC namespace, allowing inter-container communication that could lead to exploitation.

5

Is REDHAT-BUG-2270717 applicable to production environments?

Yes, REDHAT-BUG-2270717 is applicable to production environments utilizing affected container technologies, and precautions should be taken.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203