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.

The remote Rocky Linux 8 host has packages installed that are affected by a vulnerability as referenced in the RLSA-2021:0531 advisory.

  - 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. (CVE-2020-14370)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLED15 / SLES15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2022:23018-1 advisory.

  - 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. (CVE-2020-14370)

  - In containerd (an industry-standard container runtime) before version 1.2.14 there is a credential leaking     vulnerability. If a container image manifest in the OCI Image format or Docker Image V2 Schema 2 format     includes a URL for the location of a specific image layer (otherwise known as a foreign layer), the     default containerd resolver will follow that URL to attempt to download it. In v1.2.x but not 1.3.0 or     later, the default containerd resolver will provide its authentication credentials if the server where the     URL is located presents an HTTP 401 status code along with registry-specific HTTP headers. If an attacker     publishes a public image with a manifest that directs one of the layers to be fetched from a web server     they control and they trick a user or system into pulling the image, they can obtain the credentials used     for pulling that image. In some cases, this may be the user's username and password for the registry. In     other cases, this may be the credentials attached to the cloud virtual instance which can grant access to     other cloud resources in the account. The default containerd resolver is used by the cri-containerd plugin     (which can be used by Kubernetes), the ctr development tool, and other client programs that have     explicitly linked against it. This vulnerability has been fixed in containerd 1.2.14. containerd 1.3 and     later are not affected. If you are using containerd 1.3 or later, you are not affected. If you are using     cri-containerd in the 1.2 series or prior, you should ensure you only pull images from trusted sources.
    Other container runtimes built on top of containerd but not using the default resolver (such as Docker)     are not affected. (CVE-2020-15157)

  - 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. (CVE-2021-20199)

  - A deadlock vulnerability was found in 'github.com/containers/storage' in versions before 1.28.1. When a     container image is processed, each layer is unpacked using `tar`. If one of those layers is not a valid     `tar` archive this causes an error leading to an unexpected situation where the code indefinitely waits     for the tar unpacked stream, which never finishes. An attacker could use this vulnerability to craft a     malicious image, which when downloaded and stored by an application using containers/storage, would then     cause a deadlock leading to a Denial of Service (DoS). (CVE-2021-20291)

  - 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). (CVE-2021-3602)

  - 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. (CVE-2021-4024)

  - The OCI Distribution Spec project defines an API protocol to facilitate and standardize the distribution     of content. In the OCI Distribution Specification version 1.0.0 and prior, the Content-Type header alone     was used to determine the type of document during push and pull operations. Documents that contain both     manifests and layers fields could be interpreted as either a manifest or an index in the absence of an     accompanying Content-Type header. If a Content-Type header changed between two pulls of the same digest, a     client may interpret the resulting content differently. The OCI Distribution Specification has been     updated to require that a mediaType value present in a manifest or index match the Content-Type header     used during the push and pull operations. Clients pulling from a registry may distrust the Content-Type     header and reject an ambiguous document that contains both manifests and layers fields or manifests     and config fields if they are unable to update to version 1.0.1 of the spec. (CVE-2021-41190)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES15 / SLES_SAP15 host has a package installed that is affected by multiple vulnerabilities as referenced in the SUSE-SU-2022:3312-1 advisory.

  - 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. (CVE-2020-14370)

  - In containerd (an industry-standard container runtime) before version 1.2.14 there is a credential leaking     vulnerability. If a container image manifest in the OCI Image format or Docker Image V2 Schema 2 format     includes a URL for the location of a specific image layer (otherwise known as a foreign layer), the     default containerd resolver will follow that URL to attempt to download it. In v1.2.x but not 1.3.0 or     later, the default containerd resolver will provide its authentication credentials if the server where the     URL is located presents an HTTP 401 status code along with registry-specific HTTP headers. If an attacker     publishes a public image with a manifest that directs one of the layers to be fetched from a web server     they control and they trick a user or system into pulling the image, they can obtain the credentials used     for pulling that image. In some cases, this may be the user's username and password for the registry. In     other cases, this may be the credentials attached to the cloud virtual instance which can grant access to     other cloud resources in the account. The default containerd resolver is used by the cri-containerd plugin     (which can be used by Kubernetes), the ctr development tool, and other client programs that have     explicitly linked against it. This vulnerability has been fixed in containerd 1.2.14. containerd 1.3 and     later are not affected. If you are using containerd 1.3 or later, you are not affected. If you are using     cri-containerd in the 1.2 series or prior, you should ensure you only pull images from trusted sources.
    Other container runtimes built on top of containerd but not using the default resolver (such as Docker)     are not affected. (CVE-2020-15157)

  - 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. (CVE-2021-20199)

  - A deadlock vulnerability was found in 'github.com/containers/storage' in versions before 1.28.1. When a     container image is processed, each layer is unpacked using `tar`. If one of those layers is not a valid     `tar` archive this causes an error leading to an unexpected situation where the code indefinitely waits     for the tar unpacked stream, which never finishes. An attacker could use this vulnerability to craft a     malicious image, which when downloaded and stored by an application using containers/storage, would then     cause a deadlock leading to a Denial of Service (DoS). (CVE-2021-20291)

  - 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). (CVE-2021-3602)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SUSE15 host has packages installed that are affected by multiple vulnerabilities as referenced in the openSUSE-SU-2022:23018-1 advisory.

  - 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. (CVE-2020-14370)

  - In containerd (an industry-standard container runtime) before version 1.2.14 there is a credential leaking     vulnerability. If a container image manifest in the OCI Image format or Docker Image V2 Schema 2 format     includes a URL for the location of a specific image layer (otherwise known as a foreign layer), the     default containerd resolver will follow that URL to attempt to download it. In v1.2.x but not 1.3.0 or     later, the default containerd resolver will provide its authentication credentials if the server where the     URL is located presents an HTTP 401 status code along with registry-specific HTTP headers. If an attacker     publishes a public image with a manifest that directs one of the layers to be fetched from a web server     they control and they trick a user or system into pulling the image, they can obtain the credentials used     for pulling that image. In some cases, this may be the user's username and password for the registry. In     other cases, this may be the credentials attached to the cloud virtual instance which can grant access to     other cloud resources in the account. The default containerd resolver is used by the cri-containerd plugin     (which can be used by Kubernetes), the ctr development tool, and other client programs that have     explicitly linked against it. This vulnerability has been fixed in containerd 1.2.14. containerd 1.3 and     later are not affected. If you are using containerd 1.3 or later, you are not affected. If you are using     cri-containerd in the 1.2 series or prior, you should ensure you only pull images from trusted sources.
    Other container runtimes built on top of containerd but not using the default resolver (such as Docker)     are not affected. (CVE-2020-15157)

  - 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. (CVE-2021-20199)

  - A deadlock vulnerability was found in 'github.com/containers/storage' in versions before 1.28.1. When a     container image is processed, each layer is unpacked using `tar`. If one of those layers is not a valid     `tar` archive this causes an error leading to an unexpected situation where the code indefinitely waits     for the tar unpacked stream, which never finishes. An attacker could use this vulnerability to craft a     malicious image, which when downloaded and stored by an application using containers/storage, would then     cause a deadlock leading to a Denial of Service (DoS). (CVE-2021-20291)

  - 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). (CVE-2021-3602)

  - 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. (CVE-2021-4024)

  - The OCI Distribution Spec project defines an API protocol to facilitate and standardize the distribution     of content. In the OCI Distribution Specification version 1.0.0 and prior, the Content-Type header alone     was used to determine the type of document during push and pull operations. Documents that contain both     manifests and layers fields could be interpreted as either a manifest or an index in the absence of an     accompanying Content-Type header. If a Content-Type header changed between two pulls of the same digest, a     client may interpret the resulting content differently. The OCI Distribution Specification has been     updated to require that a mediaType value present in a manifest or index match the Content-Type header     used during the push and pull operations. Clients pulling from a registry may distrust the Content-Type     header and reject an ambiguous document that contains both manifests and layers fields or manifests     and config fields if they are unable to update to version 1.0.1 of the spec. (CVE-2021-41190)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Oracle Linux 8 host has packages installed that are affected by a vulnerability as referenced in the ELSA-2021-0531 advisory.

  - 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. (CVE-2020-14370)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Redhat Enterprise Linux 8 host has packages installed that are affected by a vulnerability as referenced in the RHSA-2021:0531 advisory.

  - podman: environment variables leak between containers when started via Varlink or Docker-compatible REST     API (CVE-2020-14370)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

This update for podman fixes the following issues :

Security issue fixed :

This release resolves CVE-2020-14370, in which environment variables could be leaked between containers created using the Varlink API (bsc#1176804).

Non-security issues fixed :

add dependency to timezone package or podman fails to build a container (bsc#1178122)

Install new auto-update system units

Update to v2.1.1 (bsc#1178392) :

  - Changes

  - The `podman info` command now includes the cgroup     manager Podman is using.

  - API

  - The REST API now includes a Server header in all     responses.

  - Fixed a bug where the Libpod and Compat Attach endpoints     could terminate early, before sending all output from     the container.

  - Fixed a bug where the Compat Create endpoint for     containers did not properly handle the Interactive     parameter.

  - Fixed a bug where the Compat Kill endpoint for     containers could continue to run after a fatal error.

  - Fixed a bug where the Limit parameter of the Compat List     endpoint for Containers did not properly handle a limit     of 0 (returning nothing, instead of all containers)     [#7722].

  - The Libpod Stats endpoint for containers is being     deprecated and will be replaced by a similar endpoint     with additional features in a future release.

Changes in v2.1.0

  - Features

  - A new command, `podman image mount`, has been added.
    This allows for an image to be mounted, read-only, to     inspect its contents without creating a container from     it [#1433].

  - The `podman save` and `podman load` commands can now     create and load archives containing multiple images     [#2669].

  - Rootless Podman now supports all `podman network`     commands, and rootless containers can now be joined to     networks.

  - The performance of `podman build` on `ADD` and `COPY`     instructions has been greatly improved, especially when     a `.dockerignore` is present.

  - The `podman run` and `podman create` commands now     support a new mode for the `--cgroups` option,     `--cgroups=split`. Podman will create two cgroups under     the cgroup it was launched in, one for the container and     one for Conmon. This mode is useful for running Podman     in a systemd unit, as it ensures that all processes are     retained in systemd's cgroup hierarchy [#6400].

  - The `podman run` and `podman create` commands can now     specify options to slirp4netns by using the `--network`     option as follows :

`--net slirp4netns:opt1,opt2`. This allows for, among other things,

switching the port forwarder used by slirp4netns away from rootlessport.

  - The `podman ps` command now features a new option,     `--storage`, to show containers from Buildah, CRI-O and     other applications.

  - The `podman run` and `podman create` commands now     feature a `--sdnotify` option to control the behavior of     systemd's sdnotify with containers, enabling improved     support for Podman in `Type=notify` units.

  - The `podman run` command now features a `--preserve-fds`     opton to pass file descriptors from the host into the     container

[#6458].

  - The `podman run` and `podman create` commands can now     create overlay volume mounts, by adding the `:O` option     to a bind mount

(e.g. `-v /test:/test:O`). Overlay volume mounts will mount a directory

into a container from the host and allow changes to it, but not write

those changes back to the directory on the host.

  - The `podman play kube` command now supports the Socket     HostPath type [#7112].

  - The `podman play kube` command now supports read-only     mounts.

  - The `podman play kube` command now supports setting     labels on pods from Kubernetes metadata labels.

  - The `podman play kube` command now supports setting     container restart policy [#7656].

  - The `podman play kube` command now properly handles     `HostAlias` entries.

  - The `podman generate kube` command now adds entries to     `/etc/hosts` from `--host-add` generated YAML as     `HostAlias` entries.

  - The `podman play kube` and `podman generate kube`     commands now properly support `shareProcessNamespace` to     share the PID namespace in pods.

  - The `podman volume ls` command now supports the     `dangling` filter to identify volumes that are dangling     (not attached to any container).

  - The `podman run` and `podman create` commands now     feature a `--umask` option to set the umask of the     created container.

  - The `podman create` and `podman run` commands now     feature a `--tz` option to set the timezone within the     container [#5128].

  - Environment variables for Podman can now be added in the     `containers.conf` configuration file.

  - The `--mount` option of `podman run` and `podman create`     now supports a new mount type, `type=devpts`, to add a     `devpts` mount to the container. This is useful for     containers that want to mount `/dev/` from the host into     the container, but still create a terminal.

  - The `--security-opt` flag to `podman run` and `podman     create` now supports a new option, `proc-opts`, to     specify options for the container's `/proc` filesystem.

  - Podman with the `crun` OCI runtime now supports a new     option to `podman run` and `podman create`,     `--cgroup-conf`, which allows for advanced configuration     of cgroups on cgroups v2 systems.

  - The `podman create` and `podman run` commands now     support a `--override-variant` option, to override the     architecture variant of the image that will be pulled     and ran.

  - A new global option has been added to Podman,     `--runtime-flags`, which allows for setting flags to use     when the OCI runtime is called.

  - The `podman manifest add` command now supports the     `--cert-dir`, `--auth-file`, `--creds`, and     `--tls-verify` options.

  - Security

  - This release resolves CVE-2020-14370, in which     environment variables could be leaked between containers     created using the Varlink API.

  - Changes

  - Podman will now retry pulling an image 3 times if a pull     fails due to network errors.

  - The `podman exec` command would previously print error     messages (e.g. `exec session exited with non-zero exit     code

    -1`) when the command run exited with a non-0 exit code.
    It no

longer does this. The `podman exec` command will still exit with the same

exit code as the command run in the container did.

  - Error messages when creating a container or pod with a     name that is already in use have been improved.

  - For read-only containers running systemd init, Podman     creates a tmpfs filesystem at `/run`. This was     previously limited to 65k in size and mounted `noexec`,     but is now unlimited size and mounted `exec`.

  - The `podman system reset` command no longer removes     configuration files for rootless Podman.

  - API

  - The Libpod API version has been bumped to v2.0.0 due to     a breaking change in the Image List API.

  - Docker-compatible Volume Endpoints (Create, Inspect,     List, Remove, Prune) are now available!

  - Added an endpoint for generating systemd unit files for     containers.

  - The `last` parameter to the Libpod container list     endpoint now has an alias, `limit` [#6413].

  - The Libpod image list API new returns timestamps in Unix     format, as integer, as opposed to as strings

  - The Compat Inspect endpoint for containers now includes     port information in NetworkSettings.

  - The Compat List endpoint for images now features limited     support for the (deprecated) `filter` query parameter     [#6797].

  - Fixed a bug where the Compat Create endpoint for     containers was not correctly handling bind mounts.

  - Fixed a bug where the Compat Create endpoint for     containers would not return a 404 when the requested     image was not present.

  - Fixed a bug where the Compat Create endpoint for     containers did not properly handle Entrypoint and     Command from images.

  - Fixed a bug where name history information was not     properly added in the Libpod Image List endpoint.

  - Fixed a bug where the Libpod image search endpoint     improperly populated the Description field of responses.

  - Added a `noTrunc` option to the Libpod image search     endpoint.

  - Fixed a bug where the Pod List API would return null,     instead of an empty array, when no pods were present     [#7392].

  - Fixed a bug where endpoints that hijacked would do     perform the hijack too early, before being ready to send     and receive data [#7195].

  - Fixed a bug where Pod endpoints that can operate on     multiple containers at once (e.g. Kill, Pause, Unpause,     Stop) would not forward errors from individual     containers that failed.

  - The Compat List endpoint for networks now supports     filtering results [#7462].

  - Fixed a bug where the Top endpoint for pods would return     both a 500 and 404 when run on a non-existent pod.

  - Fixed a bug where Pull endpoints did not stream progress     back to the client.

  - The Version endpoints (Libpod and Compat) now provide     version in a format compatible with Docker.

  - All non-hijacking responses to API requests should not     include headers with the version of the server.

  - Fixed a bug where Libpod and Compat Events endpoints did     not send response headers until the first event occurred     [#7263].

  - Fixed a bug where the Build endpoints (Compat and     Libpod) did not stream progress to the client.

  - Fixed a bug where the Stats endpoints (Compat and     Libpod) did not properly handle clients disconnecting.

  - Fixed a bug where the Ignore parameter to the Libpod     Stop endpoint was not performing properly.

  - Fixed a bug where the Compat Logs endpoint for     containers did not stream its output in the correct     format [#7196].

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

This update for podman fixes the following issues :

Security issue fixed :

  - This release resolves CVE-2020-14370, in which     environment variables could be leaked between containers     created using the Varlink API (bsc#1176804).

Non-security issues fixed :

  - add dependency to timezone package or podman fails to     build a container (bsc#1178122)

  - Install new auto-update system units

  - Update to v2.1.1 (bsc#1178392) :

  - Changes

  - The `podman info` command now includes the cgroup     manager Podman is using.

  - API

  - The REST API now includes a Server header in all     responses.

  - Fixed a bug where the Libpod and Compat Attach endpoints     could terminate early, before sending all output from     the container.

  - Fixed a bug where the Compat Create endpoint for     containers did not properly handle the Interactive     parameter.

  - Fixed a bug where the Compat Kill endpoint for     containers could continue to run after a fatal error.

  - Fixed a bug where the Limit parameter of the Compat List     endpoint for Containers did not properly handle a limit     of 0 (returning nothing, instead of all containers)     [#7722].

  - The Libpod Stats endpoint for containers is being     deprecated and will be replaced by a similar endpoint     with additional features in a future release.

  - Changes in v2.1.0

  - Features

  - A new command, `podman image mount`, has been added.
    This allows for an image to be mounted, read-only, to     inspect its contents without creating a container from     it [#1433].

  - The `podman save` and `podman load` commands can now     create and load archives containing multiple images     [#2669].

  - Rootless Podman now supports all `podman network`     commands, and rootless containers can now be joined to     networks.

  - The performance of `podman build` on `ADD` and `COPY`     instructions has been greatly improved, especially when     a `.dockerignore` is present.

  - The `podman run` and `podman create` commands now     support a new mode for the `--cgroups` option,     `--cgroups=split`. Podman will create two cgroups under     the cgroup it was launched in, one for the container and     one for Conmon. This mode is useful for running Podman     in a systemd unit, as it ensures that all processes are     retained in systemd's cgroup hierarchy [#6400].

  - The `podman run` and `podman create` commands can now     specify options to slirp4netns by using the `--network`     option as follows: `--net slirp4netns:opt1,opt2`. This     allows for, among other things, switching the port     forwarder used by slirp4netns away from rootlessport.

  - The `podman ps` command now features a new option,     `--storage`, to show containers from Buildah, CRI-O and     other applications.

  - The `podman run` and `podman create` commands now     feature a `--sdnotify` option to control the behavior of     systemd's sdnotify with containers, enabling improved     support for Podman in `Type=notify` units.

  - The `podman run` command now features a `--preserve-fds`     opton to pass file descriptors from the host into the     container [#6458].

  - The `podman run` and `podman create` commands can now     create overlay volume mounts, by adding the `:O` option     to a bind mount (e.g. `-v /test:/test:O`). Overlay     volume mounts will mount a directory into a container     from the host and allow changes to it, but not write     those changes back to the directory on the host.

  - The `podman play kube` command now supports the Socket     HostPath type [#7112].

  - The `podman play kube` command now supports read-only     mounts.

  - The `podman play kube` command now supports setting     labels on pods from Kubernetes metadata labels.

  - The `podman play kube` command now supports setting     container restart policy [#7656].

  - The `podman play kube` command now properly handles     `HostAlias` entries.

  - The `podman generate kube` command now adds entries to     `/etc/hosts` from `--host-add` generated YAML as     `HostAlias` entries.

  - The `podman play kube` and `podman generate kube`     commands now properly support `shareProcessNamespace` to     share the PID namespace in pods.

  - The `podman volume ls` command now supports the     `dangling` filter to identify volumes that are dangling     (not attached to any container).

  - The `podman run` and `podman create` commands now     feature a `--umask` option to set the umask of the     created container.

  - The `podman create` and `podman run` commands now     feature a `--tz` option to set the timezone within the     container [#5128].

  - Environment variables for Podman can now be added in the     `containers.conf` configuration file.

  - The `--mount` option of `podman run` and `podman create`     now supports a new mount type, `type=devpts`, to add a     `devpts` mount to the container. This is useful for     containers that want to mount `/dev/` from the host into     the container, but still create a terminal.

  - The `--security-opt` flag to `podman run` and `podman     create` now supports a new option, `proc-opts`, to     specify options for the container's `/proc` filesystem.

  - Podman with the `crun` OCI runtime now supports a new     option to `podman run` and `podman create`,     `--cgroup-conf`, which allows for advanced configuration     of cgroups on cgroups v2 systems.

  - The `podman create` and `podman run` commands now     support a `--override-variant` option, to override the     architecture variant of the image that will be pulled     and ran.

  - A new global option has been added to Podman,     `--runtime-flags`, which allows for setting flags to use     when the OCI runtime is called.

  - The `podman manifest add` command now supports the     `--cert-dir`, `--auth-file`, `--creds`, and     `--tls-verify` options.

  - Security

  - This release resolves CVE-2020-14370, in which     environment variables could be leaked between containers     created using the Varlink API.

  - Changes

  - Podman will now retry pulling an image 3 times if a pull     fails due to network errors.

  - The `podman exec` command would previously print error     messages (e.g. `exec session exited with non-zero exit     code

    -1`) when the command run exited with a non-0 exit code.
    It no longer does this. The `podman exec` command will     still exit with the same exit code as the command run in     the container did.

  - Error messages when creating a container or pod with a     name that is already in use have been improved.

  - For read-only containers running systemd init, Podman     creates a tmpfs filesystem at `/run`. This was     previously limited to 65k in size and mounted `noexec`,     but is now unlimited size and mounted `exec`.

  - The `podman system reset` command no longer removes     configuration files for rootless Podman.

  - API

  - The Libpod API version has been bumped to v2.0.0 due to     a breaking change in the Image List API.

  - Docker-compatible Volume Endpoints (Create, Inspect,     List, Remove, Prune) are now available!

  - Added an endpoint for generating systemd unit files for     containers.

  - The `last` parameter to the Libpod container list     endpoint now has an alias, `limit` [#6413].

  - The Libpod image list API new returns timestamps in Unix     format, as integer, as opposed to as strings

  - The Compat Inspect endpoint for containers now includes     port information in NetworkSettings.

  - The Compat List endpoint for images now features limited     support for the (deprecated) `filter` query parameter     [#6797].

  - Fixed a bug where the Compat Create endpoint for     containers was not correctly handling bind mounts.

  - Fixed a bug where the Compat Create endpoint for     containers would not return a 404 when the requested     image was not present.

  - Fixed a bug where the Compat Create endpoint for     containers did not properly handle Entrypoint and     Command from images.

  - Fixed a bug where name history information was not     properly added in the Libpod Image List endpoint.

  - Fixed a bug where the Libpod image search endpoint     improperly populated the Description field of responses.

  - Added a `noTrunc` option to the Libpod image search     endpoint.

  - Fixed a bug where the Pod List API would return null,     instead of an empty array, when no pods were present     [#7392].

  - Fixed a bug where endpoints that hijacked would do     perform the hijack too early, before being ready to send     and receive data [#7195].

  - Fixed a bug where Pod endpoints that can operate on     multiple containers at once (e.g. Kill, Pause, Unpause,     Stop) would not forward errors from individual     containers that failed.

  - The Compat List endpoint for networks now supports     filtering results [#7462].

  - Fixed a bug where the Top endpoint for pods would return     both a 500 and 404 when run on a non-existent pod.

  - Fixed a bug where Pull endpoints did not stream progress     back to the client.

  - The Version endpoints (Libpod and Compat) now provide     version in a format compatible with Docker.

  - All non-hijacking responses to API requests should not     include headers with the version of the server.

  - Fixed a bug where Libpod and Compat Events endpoints did     not send response headers until the first event occurred     [#7263].

  - Fixed a bug where the Build endpoints (Compat and     Libpod) did not stream progress to the client.

  - Fixed a bug where the Stats endpoints (Compat and     Libpod) did not properly handle clients disconnecting.

  - Fixed a bug where the Ignore parameter to the Libpod     Stop endpoint was not performing properly.

  - Fixed a bug where the Compat Logs endpoint for     containers did not stream its output in the correct     format [#7196].

This update was imported from the SUSE:SLE-15-SP1:Update update project.

The remote Redhat Enterprise Linux 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2020:5056 advisory.

  - golang.org/x/text: possibility to trigger an infinite loop in encoding/unicode could lead to crash     (CVE-2020-14040)

  - podman: environment variables leak between containers when started via Varlink or Docker-compatible REST     API (CVE-2020-14370)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Redhat Enterprise Linux 7 / 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2020:4297 advisory.

    The podman tool manages pods, container images, and containers. It is part of the libpod library, which is     for applications that use container pods. Container pods is a concept in Kubernetes.

    The runC tool is a lightweight, portable implementation of the Open Container Format (OCF) that provides     container runtime.

    The skopeo command lets you inspect images from container image registries, get images and image layers,     and use signatures to create and verify files.

    Security Fix(es):

    * jenkins-jira-plugin: plugin information disclosure (CVE-2019-16541)

    * jenkins-2-plugins/mailer: Missing hostname validation in Mailer Plugin could result in MITM     (CVE-2020-2252)

    * jenkins-2-plugins/blueocean: Path traversal vulnerability in Blue Ocean Plugin could allow to read     arbitrary files (CVE-2020-2254)

    * jenkins-2-plugins/blueocean: Blue Ocean Plugin does not perform permission checks in several HTTP     endpoints implementing connection tests. (CVE-2020-2255)

    * kubernetes: Docker config secrets leaked when file is malformed and loglevel >= 4 (CVE-2020-8564)

    * golang.org/x/text: possibility to trigger an infinite loop in encoding/unicode could lead to crash     (CVE-2020-14040)

    * podman: environment variables leak between containers when started via Varlink or Docker-compatible REST     API (CVE-2020-14370)

    * golang: ReadUvarint and ReadVarint can read an unlimited number of bytes from invalid inputs     (CVE-2020-16845)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

autobuilt v2.1.0,Security fix for CVE-2020-14370

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website.
Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

autobuilt v2.1.0, Security fix for CVE-2020-14370

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website.
Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

ID	Name	Product	Family	Severity
184853	Rocky Linux 8 : container-tools:rhel8 (RLSA-2021:0531)	Nessus	Rocky Linux Local Security Checks	medium
172436	SUSE SLED15 / SLES15 Security Update : conmon, libcontainers-common, libseccomp, podman (SUSE-SU-2022:23018-1)	Nessus	SuSE Local Security Checks	medium
165254	SUSE SLES15 Security Update : libcontainers-common (SUSE-SU-2022:3312-1)	Nessus	SuSE Local Security Checks	medium
158634	openSUSE 15 Security Update : conmon, libcontainers-common, libseccomp, podman (openSUSE-SU-2022:23018-1)	Nessus	SuSE Local Security Checks	medium
146640	Oracle Linux 8 : container-tools:ol8 (ELSA-2021-0531)	Nessus	Oracle Linux Local Security Checks	medium
146537	RHEL 8 : container-tools:rhel8 (RHSA-2021:0531)	Nessus	Red Hat Local Security Checks	medium
143753	SUSE SLES15 Security Update : podman (SUSE-SU-2020:3378-1)	Nessus	SuSE Local Security Checks	medium
143335	openSUSE Security Update : podman (openSUSE-2020-2039)	Nessus	SuSE Local Security Checks	medium
143322	openSUSE Security Update : podman (openSUSE-2020-2063)	Nessus	SuSE Local Security Checks	medium
142698	RHEL 7 : podman (RHSA-2020:5056)	Nessus	Red Hat Local Security Checks	medium
142002	RHEL 7 / 8 : OpenShift Container Platform 4.6.1 (RHSA-2020:4297)	Nessus	Red Hat Local Security Checks	critical
141317	Fedora 31 : 2:podman / crun (2020-3a4b8fca5e)	Nessus	Fedora Local Security Checks	medium
141140	Fedora 32 : 2:podman / crun (2020-76fcd0ba34)	Nessus	Fedora Local Security Checks	medium

Detections

Analytics

CVE-2020-14370

medium

Tenable Plugins

medium

medium

medium

medium

medium

medium

medium

medium

medium

medium

critical

medium

medium