This update for qemu fixes the following issues :

Security issue fixed :

CVE-2019-6778: Fixed a heap buffer overflow issue in the SLiRP networking implementation (bsc#1123156).

CVE-2018-16872: Fixed a host security vulnerability related to handling symlinks in usb-mtp (bsc#1119493).

CVE-2018-19489: Fixed a denial of service vulnerability in virtfs (bsc#1117275).

CVE-2018-19364: Fixed a use-after-free if the virtfs interface resulting in a denial of service (bsc#1116717).

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.

The remote Alibaba Cloud Linux 3 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALINUX3-SA-2022:0119 advisory.

    Package updates are available for Alibaba Cloud Linux 3 that fix the following vulnerabilities:

    CVE-2018-12130:
    Microarchitectural Fill Buffer Data Sampling (MFBDS): Fill buffers on some microprocessors utilizing     speculative execution may allow an authenticated user to potentially enable information disclosure via a     side channel with local access. A list of impacted products can be found here:
    https://www.intel.com/content/dam/www/public/us/en/documents/corporate-information/SA00233-microcode-     update-guidance_05132019.pdf

    CVE-2018-13405:
    The inode_init_owner function in fs/inode.c in the Linux kernel through 3.16 allows local users to create     files with an unintended group ownership, in a scenario where a directory is SGID to a certain group and     is writable by a user who is not a member of that group. Here, the non-member can trigger creation of a     plain file whose group ownership is that group. The intended behavior was that the non-member can trigger     creation of a directory (but not a plain file) whose group ownership is that group. The non-member can     escalate privileges by making the plain file executable and SGID.

    CVE-2019-10132:
    A vulnerability was found in libvirt >= 4.1.0 in the virtlockd-admin.socket and virtlogd-admin.socket     systemd units. A missing SocketMode configuration parameter allows any user on the host to connect using     virtlockd-admin-sock or virtlogd-admin-sock and perform administrative tasks against the virtlockd and     virtlogd daemons.

    CVE-2019-10161:
    It was discovered that libvirtd before versions 4.10.1 and 5.4.1 would permit read-only clients to use the     virDomainSaveImageGetXMLDesc() API, specifying an arbitrary path which would be accessed with the     permissions of the libvirtd process. An attacker with access to the libvirtd socket could use this to     probe the existence of arbitrary files, cause denial of service or cause libvirtd to execute arbitrary     programs.

    CVE-2019-10166:
    It was discovered that libvirtd, versions 4.x.x before 4.10.1 and 5.x.x before 5.4.1, would permit     readonly clients to use the virDomainManagedSaveDefineXML() API, which would permit them to modify managed     save state files. If a managed save had already been created by a privileged user, a local attacker could     modify this file such that libvirtd would execute an arbitrary program when the domain was resumed.

    CVE-2019-10167:
    The virConnectGetDomainCapabilities() libvirt API, versions 4.x.x before 4.10.1 and 5.x.x before 5.4.1,     accepts an emulatorbin argument to specify the program providing emulation for a domain. Since v1.2.19,     libvirt will execute that program to probe the domain's capabilities. Read-only clients could specify an     arbitrary path for this argument, causing libvirtd to execute a crafted executable with its own     privileges.

    CVE-2019-10168:
    The virConnectBaselineHypervisorCPU() and virConnectCompareHypervisorCPU() libvirt APIs, 4.x.x before     4.10.1 and 5.x.x before 5.4.1, accept an emulator argument to specify the program providing emulation     for a domain. Since v1.2.19, libvirt will execute that program to probe the domain's capabilities. Read-     only clients could specify an arbitrary path for this argument, causing libvirtd to execute a crafted     executable with its own privileges.

    CVE-2019-11135:
    TSX Asynchronous Abort condition on some CPUs utilizing speculative execution may allow an authenticated     user to potentially enable information disclosure via a side channel with local access.

    CVE-2019-12155:
    interface_release_resource in hw/display/qxl.c in QEMU 3.1.x through 4.0.0 has a NULL pointer dereference.

    CVE-2019-14378:
    ip_reass in ip_input.c in libslirp 4.0.0 has a heap-based buffer overflow via a large packet because it     mishandles a case involving the first fragment.

    CVE-2019-14842:
    Structured reply is a feature of the newstyle NBD protocol allowing the server to send a reply in chunks.
    A bounds check which was supposed to test for chunk offsets smaller than the beginning of the request did     not work because of signed/unsigned confusion. If one of these chunks contains a negative offset then data     under control of the server is written to memory before the read buffer supplied by the client. If the     read buffer is located on the stack then this allows the stack return address from nbd_pread() to be     trivially modified, allowing arbitrary code execution under the control of the server. If the buffer is     located on the heap then other memory objects before the buffer can be overwritten, which again would     usually lead to arbitrary code execution.

    CVE-2019-15890:
    libslirp 4.0.0, as used in QEMU 4.1.0, has a use-after-free in ip_reass in ip_input.c.

    CVE-2019-20485:
    qemu/qemu_driver.c in libvirt before 6.0.0 mishandles the holding of a monitor job during a query to a     guest agent, which allows attackers to cause a denial of service (API blockage).

    CVE-2019-6501:
    In QEMU 3.1, scsi_handle_inquiry_reply in hw/scsi/scsi-generic.c allows out-of-bounds write and read     operations.

    CVE-2019-6778:
    In QEMU 3.0.0, tcp_emu in slirp/tcp_subr.c has a heap-based buffer overflow.

    CVE-2020-10703:
    A NULL pointer dereference was found in the libvirt API responsible introduced in upstream version 3.10.0,     and fixed in libvirt 6.0.0, for fetching a storage pool based on its target path. In more detail, this     flaw affects storage pools created without a target path such as network-based pools like gluster and RBD.
    Unprivileged users with a read-only connection could abuse this flaw to crash the libvirt daemon,     resulting in a potential denial of service.

    CVE-2020-10756:
    An out-of-bounds read vulnerability was found in the SLiRP networking implementation of the QEMU emulator.
    This flaw occurs in the icmp6_send_echoreply() routine while replying to an ICMP echo request, also known     as ping. This flaw allows a malicious guest to leak the contents of the host memory, resulting in possible     information disclosure. This flaw affects versions of libslirp before 4.3.1.

    CVE-2020-11947:
    iscsi_aio_ioctl_cb in block/iscsi.c in QEMU 4.1.0 has a heap-based buffer over-read that may disclose     unrelated information from process memory to an attacker.

    CVE-2020-14301:
    An information disclosure vulnerability was found in libvirt in versions before 6.3.0. HTTP cookies used     to access network-based disks were saved in the XML dump of the guest domain. This flaw allows an attacker     to access potentially sensitive information in the domain configuration via the `dumpxml` command.

    CVE-2020-14339:
    A flaw was found in libvirt, where it leaked a file descriptor for `/dev/mapper/control` into the QEMU     process. This file descriptor allows for privileged operations to happen against the device-mapper on the     host. This flaw allows a malicious guest user or process to perform operations outside of their standard     permissions, potentially causing serious damage to the host operating system. The highest threat from this     vulnerability is to confidentiality, integrity, as well as system availability.

    CVE-2020-14364:
    An out-of-bounds read/write access flaw was found in the USB emulator of the QEMU in versions before     5.2.0. This issue occurs while processing USB packets from a guest when USBDevice 'setup_len' exceeds its     'data_buf[4096]' in the do_token_in, do_token_out routines. This flaw allows a guest user to crash the     QEMU process, resulting in a denial of service, or the potential execution of arbitrary code with the     privileges of the QEMU process on the host.

    CVE-2020-15859:
    QEMU 4.2.0 has a use-after-free in hw/net/e1000e_core.c because a guest OS user can trigger an e1000e     packet with the data's address set to the e1000e's MMIO address.

    CVE-2020-16092:
    In QEMU through 5.0.0, an assertion failure can occur in the network packet processing. This issue affects     the e1000e and vmxnet3 network devices. A malicious guest user/process could use this flaw to abort the     QEMU process on the host, resulting in a denial of service condition in net_tx_pkt_add_raw_fragment in     hw/net/net_tx_pkt.c.

    CVE-2020-1711:
    An out-of-bounds heap buffer access flaw was found in the way the iSCSI Block driver in QEMU versions     2.12.0 before 4.2.1 handled a response coming from an iSCSI server while checking the status of a Logical     Address Block (LBA) in an iscsi_co_block_status() routine. A remote user could use this flaw to crash the     QEMU process, resulting in a denial of service or potential execution of arbitrary code with privileges of     the QEMU process on the host.

    CVE-2020-1983:
    A use after free vulnerability in ip_reass() in ip_input.c of libslirp 4.2.0 and prior releases allows     crafted packets to cause a denial of service.

    CVE-2020-25637:
    A double free memory issue was found to occur in the libvirt API, in versions before 6.8.0, responsible     for requesting information about network interfaces of a running QEMU domain. This flaw affects the polkit     access control driver. Specifically, clients connecting to the read-write socket with limited ACL     permissions could use this flaw to crash the libvirt daemon, resulting in a denial of service, or     potentially escalate their privileges on the system. The highest threat from this vulnerability is to data     confidentiality and integrity as well as system availability.

    CVE-2020-25723:
    A reachable assertion issue was found in the USB EHCI emulation code of QEMU. It could occur while     processing USB requests due to missing handling of DMA memory map failure. A malicious privileged user     within the guest may abuse this flaw to send bogus USB requests and crash the QEMU process on the host,     resulting in a denial of service.

    CVE-2020-27821:
    A flaw was found in the memory management API of QEMU during the initialization of a memory region cache.
    This issue could lead to an out-of-bounds write access to the MSI-X table while performing MMIO     operations. A guest user may abuse this flaw to crash the QEMU process on the host, resulting in a denial     of service. This flaw affects QEMU versions prior to 5.2.0.

    CVE-2020-28916:
    hw/net/e1000e_core.c in QEMU 5.0.0 has an infinite loop via an RX descriptor with a NULL buffer address.

    CVE-2020-29130:
    slirp.c in libslirp through 4.3.1 has a buffer over-read because it tries to read a certain amount of     header data even if that exceeds the total packet length.

    CVE-2020-29443:
    ide_atapi_cmd_reply_end in hw/ide/atapi.c in QEMU 5.1.0 allows out-of-bounds read access because a buffer     index is not validated.

    CVE-2020-7039:
    tcp_emu in tcp_subr.c in libslirp 4.1.0, as used in QEMU 4.2.0, mismanages memory, as demonstrated by IRC     DCC commands in EMU_IRC. This can cause a heap-based buffer overflow or other out-of-bounds access which     can lead to a DoS or potential execute arbitrary code.

    CVE-2021-20257:
    An infinite loop flaw was found in the e1000 NIC emulator of the QEMU. This issue occurs while processing     transmits (tx) descriptors in process_tx_desc if various descriptor fields are initialized with invalid     values. This flaw allows a guest to consume CPU cycles on the host, resulting in a denial of service. The     highest threat from this vulnerability is to system availability.

    CVE-2021-3592:
    An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw     exists in the bootp_input() function and could occur while processing a udp packet that is smaller than     the size of the 'bootp_t' structure. A malicious guest could use this flaw to leak 10 bytes of     uninitialized heap memory from the host. The highest threat from this vulnerability is to data     confidentiality. This flaw affects libslirp versions prior to 4.6.0.

    CVE-2021-3593:
    An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw     exists in the udp6_input() function and could occur while processing a udp packet that is smaller than the     size of the 'udphdr' structure. This issue may lead to out-of-bounds read access or indirect host memory     disclosure to the guest. The highest threat from this vulnerability is to data confidentiality. This flaw     affects libslirp versions prior to 4.6.0.

    CVE-2021-3594:
    An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw     exists in the udp_input() function and could occur while processing a udp packet that is smaller than the     size of the 'udphdr' structure. This issue may lead to out-of-bounds read access or indirect host memory     disclosure to the guest. The highest threat from this vulnerability is to data confidentiality. This flaw     affects libslirp versions prior to 4.6.0.

    CVE-2021-3595:
    An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw     exists in the tftp_input() function and could occur while processing a udp packet that is smaller than the     size of the 'tftp_t' structure. This issue may lead to out-of-bounds read access or indirect host memory     disclosure to the guest. The highest threat from this vulnerability is to data confidentiality. This flaw     affects libslirp versions prior to 4.6.0.

    CVE-2021-3631:
    A flaw was found in libvirt while it generates SELinux MCS category pairs for VMs' dynamic labels. This     flaw allows one exploited guest to access files labeled for another guest, resulting in the breaking out     of sVirt confinement. The highest threat from this vulnerability is to confidentiality and integrity.

    CVE-2021-3667:
    An improper locking issue was found in the virStoragePoolLookupByTargetPath API of libvirt. It occurs in     the storagePoolLookupByTargetPath function where a locked virStoragePoolObj object is not properly     released on ACL permission failure. Clients connecting to the read-write socket with limited ACL     permissions could use this flaw to acquire the lock and prevent other users from accessing storage     pool/volume APIs, resulting in a denial of service condition. The highest threat from this vulnerability     is to system availability.

    CVE-2021-3930:
    An off-by-one error was found in the SCSI device emulation in QEMU. It could occur while processing MODE     SELECT commands in mode_sense_page() if the 'page' argument was set to MODE_PAGE_ALLS (0x3f). A malicious     guest could use this flaw to potentially crash QEMU, resulting in a denial of service condition.

Tenable has extracted the preceding description block directly from the Alibaba Cloud 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.

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

    Kernel-based Virtual Machine (KVM) is a full virtualization solution for Linux on a variety of     architectures. The qemu-kvm packages provide the user-space component for running virtual machines that     use KVM.

    Security Fix(es):

    * QEMU: slirp: heap buffer overflow while reassembling fragmented datagrams (CVE-2018-11806)

    * QEMU: slirp: heap buffer overflow in tcp_emu() (CVE-2019-6778)

    * QEMU: ne2000: integer overflow leads to buffer overflow issue (CVE-2018-10839)

    * QEMU: pcnet: integer overflow leads to buffer overflow (CVE-2018-17962)

    * QEMU: qxl: null pointer dereference while releasing spice resources (CVE-2019-12155)

    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.

The remote NewStart CGSL host, running version MAIN 4.06, has qemu-kvm packages installed that are affected by multiple vulnerabilities:

  - m_cat in slirp/mbuf.c in Qemu has a heap-based buffer     overflow via incoming fragmented datagrams.
    (CVE-2018-11806)

  - Qemu emulator <= 3.0.0 built with the NE2000 NIC     emulation support is vulnerable to an integer overflow,     which could lead to buffer overflow issue. It could     occur when receiving packets over the network. A user     inside guest could use this flaw to crash the Qemu     process resulting in DoS. (CVE-2018-10839)

  - Qemu has a Buffer Overflow in pcnet_receive in     hw/net/pcnet.c because an incorrect integer data type is     used. (CVE-2018-17962)

  - In QEMU 3.0.0, tcp_emu in slirp/tcp_subr.c has a heap-     based buffer overflow. (CVE-2019-6778)

  - interface_release_resource in hw/display/qxl.c in QEMU     4.0.0 has a NULL pointer dereference. (CVE-2019-12155)

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

This is a version update for podman to version 1.4.4 (bsc#1143386).

Additional changes by SUSE on top :

Remove fuse-overlayfs because it's (currently) an unsatisfied dependency on SLE (bsc#1143386)

Update libpod.conf to use correct infra_command

Update libpod.conf to use better versioned pause container

Update libpod.conf to use official kubic pause container

Update libpod.conf to match latest features set: detach_keys, lock_type, runtime_supports_json

Add podman-remote varlink client

Version update podman to v1.4.4: Features

  - Podman now has greatly improved support for containers     using multiple OCI runtimes. Containers now remember if     they were created with a different runtime using
    --runtime and will always use that runtime

  - The cached and delegated options for volume mounts are     now allowed for Docker compatability (#3340)

  - The podman diff command now supports the --latest flag     Bugfixes

  - Fixed a bug where rootless Podman would attempt to use     the entire root configuration if no rootless     configuration was present for the user, breaking     rootless Podman for new installations

  - Fixed a bug where rootless Podman's pause process would     block SIGTERM, preventing graceful system shutdown and     hanging until the system's init send SIGKILL

  - Fixed a bug where running Podman as root with sudo -E     would not work after running rootless Podman at least     once

  - Fixed a bug where options for tmpfs volumes added with     the --tmpfs flag were being ignored

  - Fixed a bug where images with no layers could not     properly be displayed and removed by Podman

  - Fixed a bug where locks were not properly freed on     failure to create a container or pod

  - Fixed a bug where podman cp on a single file would     create a directory at the target and place the file in     it (#3384)

  - Fixed a bug where podman inspect --format '{{.Mounts}}'     would print a hexadecimal address instead of a     container's mounts

  - Fixed a bug where rootless Podman would not add an entry     to container's /etc/hosts files for their own hostname     (#3405)

  - Fixed a bug where podman ps --sync would segfault     (#3411)

  - Fixed a bug where podman generate kube would produce an     invalid ports configuration (#3408) Misc

  - Updated containers/storage to v1.12.13

  - Podman now performs much better on systems with heavy     I/O load

  - The --cgroup-manager flag to podman now shows the     correct default setting in help if the default was     overridden by libpod.conf

  - For backwards compatability, setting
    --log-driver=json-file in podman run is now supported as     an alias for --log-driver=k8s-file. This is considered     deprecated, and json-file will be moved to a new     implementation in the future     ([#3363](https://github.com/containers/libpo\     d/issues/3363))

  - Podman's default libpod.conf file now allows the crun     OCI runtime to be used if it is installed

Update podman to v1.4.2: Fixed a bug where Podman could not run containers using an older version of Systemd as init

Updated vendored Buildah to v1.9.0 to resolve a critical bug with Dockerfile RUN instructions

The error message for running podman kill on containers that are not running has been improved

Podman remote client can now log to a file if syslog is not available

The podman exec command now sets its error code differently based on whether the container does not exist, and the command in the container does not exist

The podman inspect command on containers now outputs Mounts JSON that matches that of docker inspect, only including user-specified volumes and differentiating bind mounts and named volumes

The podman inspect command now reports the path to a container's OCI spec with the OCIConfigPath key (only included when the container is initialized or running)

The podman run --mount command now supports the bind-nonrecursive option for bind mounts

Fixed a bug where podman play kube would fail to create containers due to an unspecified log driver

Fixed a bug where Podman would fail to build with musl libc

Fixed a bug where rootless Podman using slirp4netns networking in an environment with no nameservers on the host other than localhost would result in nonfunctional networking

Fixed a bug where podman import would not properly set environment variables, discarding their values and retaining only keys

Fixed a bug where Podman would fail to run when built with Apparmor support but run on systems without the Apparmor kernel module loaded

Remote Podman will now default the username it uses to log in to remote systems to the username of the current user

Podman now uses JSON logging with OCI runtimes that support it, allowing for better error reporting

Updated vendored containers/image to v2.0

Update conmon to v0.3.0

Support OOM Monitor under cgroup V2

Add config binary and make target for configuring conmon with a go library for importing values

Updated podman to version 1.4.0 (bsc#1137860) and (bsc#1135460) Podman checkpoint and podman restore commands can now be used to migrate containers between Podman installations on different systems.

The podman cp now supports pause flag.

The remote client now supports a configuration file for pre-configuring connections to remote Podman installations

CVE-2019-10152: Fixed an iproper dereference of symlinks of the the podman cp command which introduced in version 1.1.0 (bsc#1136974).

Fixed a bug where podman commit could improperly set environment variables that contained = characters

Fixed a bug where rootless podman would sometimes fail to start containers with forwarded ports

Fixed a bug where podman version on the remote client could segfault

Fixed a bug where podman container runlabel would use /proc/self/exe instead of the path of the Podman command when printing the command being executed

Fixed a bug where filtering images by label did not work

Fixed a bug where specifying a bing mount or tmpfs mount over an image volume would cause a container to be unable to start

Fixed a bug where podman generate kube did not work with containers with named volumes

Fixed a bug where rootless podman would receive permission denied errors accessing conmon.pid

Fixed a bug where podman cp with a folder specified as target would replace the folder, as opposed to copying into it

Fixed a bug where rootless Podman commands could double-unlock a lock, causing a crash

Fixed a bug where podman incorrectly set tmpcopyup on /dev/ mounts, causing errors when using the Kata containers runtime

Fixed a bug where podman exec would fail on older kernels

Podman commit command is now usable with the Podman remote client

Signature-policy flag has been deprecated

Updated vendored containers/storage and containers/image libraries with numerous bugfixes

Updated vendored Buildah to v1.8.3

Podman now requires Conmon v0.2.0

The podman cp command is now aliased as podman container cp

Rootless podman will now default init_path using root Podman's configuration files (/etc/containers/libpod.conf and /usr/share/containers/libpod.conf) if not overridden in the rootless configuration

Added fuse-overlayfs dependency to support overlay based rootless image manipulations

The podman cp command can now read input redirected to STDIN, and output to STDOUT instead of a file, using - instead of an argument.

The podman remote client now displays version information from both the client and server in podman version

The podman unshare command has been added, allowing easy entry into the user namespace set up by rootless Podman (allowing the removal of files created by rootless podman, among other things)

Fixed a bug where Podman containers with the --rm flag were removing created volumes when they were automatically removed

Fixed a bug where container and pod locks were incorrectly marked as released after a system reboot, causing errors on container and pod removal

Fixed a bug where Podman pods could not be removed if any container in the pod encountered an error during removal

Fixed a bug where Podman pods run with the cgroupfs CGroup driver would encounter a race condition during removal, potentially failing to remove the pod CGroup

Fixed a bug where the podman container checkpoint and podman container restore commands were not visible in the remote client

Fixed a bug where podman remote ps --ns would not print the container's namespaces

Fixed a bug where removing stopped containers with healthchecks could cause an error

Fixed a bug where the default libpod.conf file was causing parsing errors

Fixed a bug where pod locks were not being freed when pods were removed, potentially leading to lock exhaustion

Fixed a bug where 'podman run' with SD_NOTIFY set could, on short-running containers, create an inconsistent state rendering the container unusable

The remote Podman client now uses the Varlink bridge to establish remote connections by default

Fixed an issue with apparmor_parser (bsc#1123387)

Update to libpod v1.4.0 (bsc#1137860) :

The podman checkpoint and podman restore commands can now be used to migrate containers between Podman installations on different systems

The podman cp command now supports a pause flag to pause containers while copying into them

The remote client now supports a configuration file for pre-configuring connections to remote Podman installations

Fixed CVE-2019-10152 - The podman cp command improperly dereferenced symlinks in host context

Fixed a bug where podman commit could improperly set environment variables that contained = characters

Fixed a bug where rootless Podman would sometimes fail to start containers with forwarded ports

Fixed a bug where podman version on the remote client could segfault

Fixed a bug where podman container runlabel would use /proc/self/exe instead of the path of the Podman command when printing the command being executed

Fixed a bug where filtering images by label did not work

Fixed a bug where specifying a bing mount or tmpfs mount over an image volume would cause a container to be unable to start

Fixed a bug where podman generate kube did not work with containers with named volumes

Fixed a bug where rootless Podman would receive permission denied errors accessing conmon.pid

Fixed a bug where podman cp with a folder specified as target would replace the folder, as opposed to copying into it

Fixed a bug where rootless Podman commands could double-unlock a lock, causing a crash

Fixed a bug where Podman incorrectly set tmpcopyup on /dev/ mounts, causing errors when using the Kata containers runtime

Fixed a bug where podman exec would fail on older kernels

The podman commit command is now usable with the Podman remote client

The --signature-policy flag (used with several image-related commands) has been deprecated

The podman unshare command now defines two environment variables in the spawned shell: CONTAINERS_RUNROOT and CONTAINERS_GRAPHROOT, pointing to temporary and permanent storage for rootless containers

Updated vendored containers/storage and containers/image libraries with numerous bugfixes

Updated vendored Buildah to v1.8.3

Podman now requires Conmon v0.2.0

The podman cp command is now aliased as podman container cp

Rootless Podman will now default init_path using root Podman's configuration files (/etc/containers/libpod.conf and /usr/share/containers/libpod.conf) if not overridden in the rootless configuration

Update to image v1.5.1

Vendor in latest containers/storage

docker/docker_client: Drop redundant Domain(ref.ref) call

pkg/blobinfocache: Split implementations into subpackages

copy: progress bar: show messages on completion

docs: rename manpages to *.5.command

add container-certs.d.md manpage

pkg/docker/config: Bring auth tests from docker/docker_client_test

Don't allocate a sync.Mutex separately

Update to storage v1.12.10: Add function to parse out mount options from graphdriver

Merge the disparate parts of all of the Unix-like lockfiles

Fix unix-but-not-Linux compilation

Return XDG_RUNTIME_DIR as RootlessRuntimeDir if set

Cherry-pick moby/moby #39292 for CVE-2018-15664 fixes

lockfile: add RecursiveLock() API

Update generated files

Fix crash on tesing of aufs code

Let consumers know when Layers and Images came from read-only stores

chown: do not change owner for the mountpoint

locks: correctly mark updates to the layers list

CreateContainer: don't worry about mapping layers unless necessary

docs: fix manpage for containers-storage.conf

docs: sort configuration options alphabetically

docs: document OSTree file deduplication

Add missing options to man page for containers-storage

overlay: use the layer idmapping if present

vfs: prefer layer custom idmappings

layers: propagate down the idmapping settings

Recreate symlink when not found

docs: fix manpage for configuration file

docs: add special handling for manpages in sect 5

overlay: fix single-lower test

Recreate symlink when not found

overlay: propagate errors from mountProgram

utils: root in a userns uses global conf file

Fix handling of additional stores

Correctly check permissions on rootless directory

Fix possible integer overflow on 32bit builds

Evaluate device path for lvm

lockfile test: make concurrent RW test determinisitc

lockfile test: make concurrent read tests deterministic

drivers.DirCopy: fix filemode detection

storage: move the logic to detect rootless into utils.go

Don't set (struct flock).l_pid

Improve documentation of getLockfile

Rename getLockFile to createLockerForPath, and document it

Add FILES section to containers-storage.5 man page

add digest locks

drivers/copy: add a non-cgo fallback

slirp4netns was updated to 0.3.0: CVE-2019-6778: Fixed a heap buffer overflow in tcp_emu() (bsc#1123156)

This update also includes: fuse3 and fuse-overlayfs to support rootless containers.

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.

Multiple security issues were discovered in QEMU, a fast processor emulator, which could result in denial of service, the execution of arbitrary code or information disclosure.

In addition this update backports support to passthrough the new md-clear CPU flag added in the intel-microcode update shipped in DSA 4447 to x86-based guests.

This update for xen fixes the following issues :

Security issues fixed :

Fixed multiple access violations introduced by XENMEM_exchange hypercall which could allow a single PV guest to leak arbitrary amounts of memory, leading to a denial of service (bsc#1126192).

Fixed an issue which could allow a malicious unprivileged guest userspace process to escalate its privilege to that of other userspace processes in the same guest and potentially thereby to that of the guest operating system (bsc#1126201).

Fixed an issue which could allow an untrusted PV domain with access to a physical device to DMA into its own pagetables leading to privilege escalation (bsc#1126195).

Fixed an issue which could allow a malicious or buggy x86 PV guest kernels can mount a Denial of Service attack affecting the whole system (bsc#1126196).

CVE-2019-6778: Fixed a heap buffer overflow in tcp_emu() found in slirp (bsc#1123157).

Fixed an issue which could allow malicious PV guests may cause a host crash or gain access to data pertaining to other guests.Additionally, vulnerable configurations are likely to be unstable even in the absence of an attack (bsc#1126198).

Fixed an issue which could allow malicious 64bit PV guests to cause a host crash (bsc#1127400).

Fixed an issue which could allow malicious or buggy guests with passed through PCI devices to be able to escalate their privileges, crash the host, or access data belonging to other guests. Additionally memory leaks were also possible (bsc#1126140).

Fixed a race condition issue which could allow malicious PV guests to escalate their privilege to that of the hypervisor (bsc#1126141).

CVE-2019-9824: Fixed an information leak in SLiRP networking implementation which could allow a user/process to read uninitialised stack memory contents (bsc#1129623).

Other issues fixed: Fixed an issue where VMs crashing when migrating between dom0 hosts (bsc#1031382).

Upstream bug fixes (bsc#1027519)

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 xen fixes the following issues :

Security issues fixed :

  - CVE-2018-19967: Fixed HLE constructs that allowed guests     to lock up the host, resulting in a Denial of Service     (DoS). (XSA-282) (bsc#1114988)

  - CVE-2019-6778: Fixed a heap buffer overflow in tcp_emu()     found in slirp (bsc#1123157).

  - Fixed an issue which could allow malicious or buggy     guests with passed through PCI devices to be able to     escalate their privileges, crash the host, or access     data belonging to other guests. Additionally memory     leaks were also possible (bsc#1126140).

  - Fixed a race condition issue which could allow malicious     PV guests to escalate their privilege to that of the     hypervisor (bsc#1126141).

  - Fixed an issue which could allow a malicious     unprivileged guest userspace process to escalate its     privilege to that of other userspace processes in the     same guest and potentially thereby to that of the guest     operating system (bsc#1126201).

  - CVE-2019-9824: Fixed an information leak in SLiRP     networking implementation which could allow a     user/process to read uninitialised stack memory contents     (bsc#1129623).

  - CVE-2018-19961 CVE-2018-19962: Fixed insufficient TLB     flushing / improper large page mappings with AMD IOMMUs     (XSA-275)(bsc#1115040).

  - CVE-2018-19965: Fixed denial of service issue from     attempting to use INVPCID with a non-canonical addresses     (XSA-279)(bsc#1115045).

  - CVE-2018-19966: Fixed issue introduced by XSA-240 that     could have caused conflicts with shadow paging     (XSA-280)(bsc#1115047).

  - Fixed an issue which could allow malicious PV guests may     cause a host crash or gain access to data pertaining to     other guests.Additionally, vulnerable configurations are     likely to be unstable even in the absence of an attack     (bsc#1126198).

  - Fixed multiple access violations introduced by     XENMEM_exchange hypercall which could allow a single PV     guest to leak arbitrary amounts of memory, leading to a     denial of service (bsc#1126192).

  - Fixed an issue which could allow malicious 64bit PV     guests to cause a host crash (bsc#1127400).

  - Fixed an issue which could allow malicious or buggy x86     PV guest kernels to mount a Denial of Service attack     affecting the whole system (bsc#1126197).

  - Fixed an issue which could allow an untrusted PV domain     with access to a physical device to DMA into its own     pagetables leading to privilege escalation     (bsc#1126195).

  - Fixed an issue which could allow a malicious or buggy     x86 PV guest kernels can mount a Denial of Service     attack affecting the whole system (bsc#1126196).

Other issues addressed :

  - Upstream bug fixes (bsc#1027519)

  - Fixed an issue where live migrations were failing when     spectre was enabled on xen boot cmdline (bsc#1116380).

  - Fixed an issue where setup of grant_tables and other     variables may fail (bsc#1126325).

  - Fixed a building issue (bsc#1119161).

  - Fixed an issue where xpti=no-dom0 was not working as     expected (bsc#1105528).

  - Packages should no longer use /var/adm/fillup-templates     (bsc#1069468). 

  - Added Xen cmdline option 'suse_vtsc_tolerance' to avoid     TSC emulation for HVM domUs (bsc#1026236).

This update was imported from the SUSE:SLE-12-SP3:Update update project.

ID	名稱	產品	系列	已發布	已更新	嚴重性
122419	SUSE SLES12 Security Update : qemu (SUSE-SU-2019:0471-1)	Nessus	SuSE Local Security Checks	2019/2/25	2024/6/18	high
236436	Alibaba Cloud Linux 3 : 0119: virt:rhel and virt-devel:rhel (ALINUX3-SA-2022:0119)	Nessus	Alibaba Cloud Linux Local Security Checks	2025/5/14	2025/5/15	critical
129332	RHEL 6 : qemu-kvm (RHSA-2019:2892)	Nessus	Red Hat Local Security Checks	2019/9/25	2024/11/6	high
131771	NewStart CGSL MAIN 4.06 : qemu-kvm Multiple Vulnerabilities (NS-SA-2019-0211)	Nessus	NewStart CGSL Local Security Checks	2019/12/6	2024/4/5	high
128302	SUSE SLES15 Security Update : podman, slirp4netns / libcontainers-common (SUSE-SU-2019:2223-1)	Nessus	SuSE Local Security Checks	2019/8/28	2024/4/30	high
125609	Debian DSA-4454-1 : qemu - security update	Nessus	Debian Local Security Checks	2019/5/31	2024/5/17	high
123637	SUSE SLES11 Security Update : xen (SUSE-SU-2019:14001-1)	Nessus	SuSE Local Security Checks	2019/4/2	2022/1/26	high
124147	openSUSE Security Update : xen (openSUSE-2019-1226)	Nessus	SuSE Local Security Checks	2019/4/18	2024/5/31	high

偵測

搜尋 Plugin

high

critical

high

high

high

high

high

high