Skip to content
OpenAdvisories
Medium SUSE-SU-2022:3312-1 5 CVEs

Security update for libcontainers-common

Published Sep 19, 2022 · Updated Feb 4, 2026

Summary

This update for libcontainers-common fixes the following issues:

libcontainers-common was updated:

- common component was updated to 0.44.0.
- storage component was updated to 1.36.0.
- image component was updated to 5.16.0.
- podman component was updated to 3.3.1.

3.3.1:

Bugfixes:

- Fixed a bug where unit files created by `podman generate systemd` could not cleanup shut down containers when stopped by `systemctl stop` .
- Fixed a bug where `podman machine` commands would not properly locate the `gvproxy` binary in some circumstances.
- Fixed a bug where containers created as part of a pod using the `--pod-id-file` option would not join the pod's network namespace .
- Fixed a bug where Podman, when using the systemd cgroups driver, could sometimes leak dbus sessions.
- Fixed a bug where the `until` filter to `podman logs` and `podman events` was improperly handled, requiring input to be negated .
- Fixed a bug where rootless containers using CNI networking run on systems using `systemd-resolved` for DNS would fail to start if resolved symlinked `/etc/resolv.conf` to an absolute path .

API:

- A large number of potential file descriptor leaks from improperly closing client connections have been fixed.

3.3.0:

Features:

- Containers inside VMs created by `podman machine` will now automatically handle port forwarding - containers in `podman machine` VMs that publish ports via `--publish` or `--publish-all` will have these ports not just forwarded on the VM, but also on the host system.
- The `podman play kube` command's `--network` option now accepts advanced network options (e.g. `--network slirp4netns:port_handler=slirp4netns`) .
- The `podman play kube` commmand now supports Kubernetes liveness probes, which will be created as Podman healthchecks.
- Podman now provides a systemd unit, `podman-restart.service`, which, when enabled, will restart all containers that were started with `--restart=always` after the system reboots.
- Rootless Podman can now be configured to use CNI networking by default by using the `rootless_networking` option in `containers.conf`.
- Images can now be pulled using `image:tag@digest` syntax (e.g. `podman pull fedora:34@sha256:1b0d4ddd99b1a8c8a80e885aafe6034c95f266da44ead992aab388e6aa91611a`) .
- The `podman container checkpoint` and `podman container restore` commands can now be used to checkpoint containers that are in pods, and restore those containers into pods.
- The `podman container restore` command now features a new option, `--publish`, to change the ports that are forwarded to a container that is being restored from an exported checkpoint.
- The `podman container checkpoint` command now features a new option, `--compress`, to specify the compression algorithm that will be used on the generated checkpoint.
- The `podman pull` command can now pull multiple images at once (e.g. `podman pull fedora:34 ubi8:latest` will pull both specified images).
- THe `podman cp` command can now copy files from one container into another directly (e.g. `podman cp containera:/etc/hosts containerb:/etc/`) .
- The `podman cp` command now supports a new option, `--archive`, which controls whether copied files will be chown'd to the UID and GID of the user of the destination container.
- The `podman stats` command now provides two additional metrics: Average CPU, and CPU time.
- The `podman pod create` command supports a new flag, `--pid`, to specify the PID namespace of the pod. If specified, containers that join the pod will automatically share its PID namespace.
- The `podman pod create` command supports a new flag, `--infra-name`, which allows the name of the pod's infra container to be set .
- The `podman auto-update` command has had its output reformatted - it is now much clearer what images were pulled and what containers were updated.
- The `podman auto-update` command now supports a new option, `--dry-run`, which reports what would be updated but does not actually perform the update .
- The `podman build` command now supports a new option, `--secret`, to mount secrets into build containers.
- The `podman manifest remove` command now has a new alias, `podman manifest rm`.
- The `podman login` command now supports a new option, `--verbose`, to print detailed information about where the credentials entered were stored.
- The `podman events` command now supports a new event, `exec_died`, which is produced when an exec session exits, and includes the exit code of the exec session.
- The `podman system connection add` command now supports adding connections that connect using the `tcp://` and `unix://` URL schemes.
- The `podman system connection list` command now supports a new flag, `--format`, to determine how the output is printed.
- The `podman volume prune` and `podman volume ls` commands' `--filter` option now support a new filter, `until`, that matches volumes created before a certain time .
- The `podman ps --filter` option's `network` filter now accepts a new value: `container:`, which matches containers that share a network namespace with a specific container .
- The `podman diff` command can now accept two arguments, allowing two images or two containers to be specified; the diff between the two will be printed .
- Podman can now optionally copy-up content from containers into volumes mounted into those containers earlier (at creation time, instead of at runtime) via the `prepare_on_create` option in `containers.conf` .
- A new option, `--gpus`, has been added to `podman create` and `podman run` as a no-op for better compatibility with Docker. If the nvidia-container-runtime package is installed, GPUs should be automatically added to containers without using the flag.
- If an invalid subcommand is provided, similar commands to try will now be suggested in the error message.
### Changes
- The `podman system reset` command now removes non-Podman (e.g. Buildah and CRI-O) containers as well.
- The new port forwarding offered by `podman machine` requires [gv

Fixed packages 15

ReleasePackageFixed in
SUSE · Enterprise Storage 6 libcontainers-common 20210626-150100.3.15.1
SUSE · Enterprise Storage 7 libcontainers-common 20210626-150100.3.15.1
SUSE · SLE HPC 15 SP1 Linux Enterprise High Performance Computing 15 SP1-ESPOS libcontainers-common 20210626-150100.3.15.1
SUSE · SLE HPC 15 SP1 Linux Enterprise High Performance Computing 15 SP1-LTSS libcontainers-common 20210626-150100.3.15.1
SUSE · SLE HPC 15 SP2 Linux Enterprise High Performance Computing 15 SP2-ESPOS libcontainers-common 20210626-150100.3.15.1
SUSE · SLE HPC 15 SP2 Linux Enterprise High Performance Computing 15 SP2-LTSS libcontainers-common 20210626-150100.3.15.1
SUSE · SLES 15 SP1 Linux Enterprise Server 15 SP1-BCL libcontainers-common 20210626-150100.3.15.1
SUSE · SLES 15 SP1 Linux Enterprise Server 15 SP1-LTSS libcontainers-common 20210626-150100.3.15.1
SUSE · SLES 15 SP2 Linux Enterprise Server 15 SP2-BCL libcontainers-common 20210626-150100.3.15.1
SUSE · SLES 15 SP2 Linux Enterprise Server 15 SP2-LTSS libcontainers-common 20210626-150100.3.15.1
SUSE · SLES for SAP 15 SP1 Linux Enterprise Server for SAP Applications 15 SP1 libcontainers-common 20210626-150100.3.15.1
SUSE · SLES for SAP 15 SP2 Linux Enterprise Server for SAP Applications 15 SP2 libcontainers-common 20210626-150100.3.15.1
SUSE · Manager Proxy 4.1 libcontainers-common 20210626-150100.3.15.1
SUSE · Manager Retail Branch Server 4.1 libcontainers-common 20210626-150100.3.15.1
SUSE · Manager Server 4.1 libcontainers-common 20210626-150100.3.15.1

Vulnerabilities 5

References

  • report
    https://bugzilla.suse.com/1176804
  • report
    https://bugzilla.suse.com/1177598
  • report
    https://bugzilla.suse.com/1181640
  • report
    https://bugzilla.suse.com/1182998
  • report
    https://bugzilla.suse.com/1188520
  • report
    https://bugzilla.suse.com/1189893
  • web
    https://www.suse.com/security/cve/CVE-2020-14370
  • web
    https://www.suse.com/security/cve/CVE-2020-15157
  • web
    https://www.suse.com/security/cve/CVE-2021-20199
  • web
    https://www.suse.com/security/cve/CVE-2021-20291
  • web
    https://www.suse.com/security/cve/CVE-2021-3602