Podman's default inheritable capabilities for linux container not empty
podman
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/containers/podman/v4 Go |
|
|
| github.com/containers/podman Go |
| No fix yet |
| github.com/containers/podman/v2 Go |
|
podman
| Product | Affected | Fixed in |
|---|---|---|
| github.com/containers/podman/v4 Go |
|
|
| github.com/containers/podman Go |
| No fix yet |
| github.com/containers/podman/v2 Go |
|
| No fix yet |
| github.com/containers/podman/v3 Go |
| No fix yet |
A flaw was found in Podman, where containers were started incorrectly with non-empty default permissions. A vulnerability was found in Moby (Docker Engine), where containers were started incorrectly with non-empty inheritable Linux process capabilities. This flaw allows an attacker with access to programs with inheritable file capabilities to elevate those capabilities to the permitted set when execve(2) runs.
From the CVE record · redhat
Podman can start containers with non-empty default permissions. An attacker with access to programs that have inheritable file capabilities can elevate those capabilities to the permitted set when execve(2) runs. The input does not specify an authentication requirement or user interaction.
Check users of Go package github.com/containers/podman/v4 before 4.0.3 and users of github.com/containers/podman, github.com/containers/podman/v2, or github.com/containers/podman/v3 at any version.