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 host's 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 host's services by forwarding all ports to the VM.
Fix in 3.4.3, please stabilize if suitable.
Yes, please stabilize app-containers/podman-3.4.4.
(In reply to Zac Medico from comment #1)
> Yes, please stabilize app-containers/podman-3.4.4.
Thanks Zac! Filed a separate bug as we changed the workflow recently
The bug has been closed via the following commit(s):
Author: Zac Medico <firstname.lastname@example.org>
AuthorDate: 2021-12-27 03:30:03 +0000
Commit: Zac Medico <email@example.com>
CommitDate: 2021-12-27 03:30:24 +0000
app-containers/podman: Remove vulnerable version
Package-Manager: Portage-3.0.30, Repoman-3.0.3
Signed-off-by: Zac Medico <firstname.lastname@example.org>
app-containers/podman/Manifest | 1 -
app-containers/podman/podman-3.4.1.ebuild | 164 ------------------------------
2 files changed, 165 deletions(-)