p PatchFirst

PatchFirst · Latest vulnerabilities

podman vulnerabilities

Vulnerabilities published for podman in the last 30 days: 0. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 4

  1. CVE-2021-3602

    Medium · CVSS 5.5EPSS 0.32%Fix available

    CVE-2021-3602

    An information disclosure flaw was found in Buildah, when building containers using chroot isolation. Running processes in container builds (e.g. Dockerfile RUN commands) can access environment variables from parent and grandparent processes. When run in a container in a CI/CD environment, environment variables may include sensitive information that was shared with the container in order to be used only by Buildah itself (e.g. container registry credentials).

    • Update to 3.2.3-r0
    Published Updated
  2. CVE-2021-20199

    Medium · CVSS 5.9EPSS 1.11%Fix available

    CVE-2021-20199

    Rootless containers run with Podman, receive all traffic with a source IP address of 127.0.0.1 (including from remote hosts). This impacts containerized applications that trust localhost (127.0.01) connections by default and do not require authentication. This issue affects Podman 1.8.0 onwards.

    • Update to 3.0.0-r0
    Published Updated
  3. CVE-2020-14370

    Medium · CVSS 5.3EPSS 1.4%Fix available

    CVE-2020-14370

    An information disclosure vulnerability was found in containers/podman in versions before 2.0.5. When using the deprecated Varlink API or the Docker-compatible REST API, if multiple containers are created in a short duration, the environment variables from the first container will get leaked into subsequent containers. An attacker who has control over the subsequent containers could use this flaw to gain access to sensitive information stored in such variables.

    • Update to 2.0.5-r0
    Published Updated
  4. CVE-2020-1726

    Medium · CVSS 5.9EPSS 1.53%Fix available

    CVE-2020-1726

    A flaw was discovered in Podman where it incorrectly allows containers when created to overwrite existing files in volumes, even if they are mounted as read-only. When a user runs a malicious container or a container based on a malicious image with an attached volume that is used for the first time, it is possible to trigger the flaw and overwrite files in the volume.This issue was introduced in version 1.6.0.

    • Update to 1.8.1-r0
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →