PowerShell Command Injection in Podman HyperV Machine
containers podman
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/containers/podman/v4 Go |
| No fix yet |
| github.com/containers/podman/v5 Go |
|
|
| github.com/containers/podman |
containers podman
| Product | Affected | Fixed in |
|---|---|---|
| github.com/containers/podman/v4 Go |
| No fix yet |
| github.com/containers/podman/v5 Go |
|
|
| github.com/containers/podman |
|
| No fix yet |
| github.com/containers/podman/v2 Go |
| No fix yet |
| github.com/containers/podman/v3 Go |
| No fix yet |
Podman is a tool for managing OCI containers and pods. Versions 4.8.0 through 5.8.1 contain a command injection vulnerability in the HyperV machine backend in pkg/machine/hyperv/stubber.go, where the VM image path is inserted into a PowerShell double-quoted string without sanitization, allowing $() subexpression injection. Because PowerShell evaluates subexpressions inside double-quoted strings before executing the outer command, an attacker who can control the VM image path through a crafted machine name or image directory can execute arbitrary PowerShell commands with the privileges of the Podman process. On typical Windows installations this means SYSTEM-level code execution, and only Windows is affected as the code is exclusive to the HyperV backend. This issue has been patched in version 5.8.2.
From the CVE record · GitHub_M
Podman versions 4.8.0 through 5.8.1 on Windows are vulnerable to command injection in the HyperV machine backend. An attacker who can control the VM image path through a crafted machine name or image directory can execute PowerShell commands with the privileges of the Podman process; the input does not specify authentication or user-interaction requirements.
Check Windows HyperV users running Podman 4.8.0 through 5.8.1, including affected Go packages github.com/containers/podman/v4 and github.com/containers/podman/v5.