A flaw was found in podman. The podman machine function (used to create and manage Podman virtual machine containing a Podman process) spawns a gvproxy process on the host system. The gvproxy API is accessible on port 7777 on all IP addresses on the host. If that port is open on the hosts firewall, an attacker can potentially use the gvproxy API to forward ports on the host to ports in the VM, making private services on the VM accessible to the network. This issue could be also used to interrupt the hosts services by forwarding all ports to the VM.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Podman | Podman_project | 3.3.0 (including) | 3.4.3 (excluding) |
| Libpod | Ubuntu | hirsute | * |
| Libpod | Ubuntu | impish | * |
| Libpod | Ubuntu | kinetic | * |
| Libpod | Ubuntu | lunar | * |
| Libpod | Ubuntu | mantic | * |
| Libpod | Ubuntu | trusty | * |
| Libpod | Ubuntu | xenial | * |
| Red Hat Enterprise Linux 8 | RedHat | container-tools:rhel8-8100020241101101019.afee755d | * |
| Red Hat Enterprise Linux 9 | RedHat | podman-2:4.2.0-3.el9 | * |
There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:
Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:
Information exposures can occur in different ways:
It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.