SUSE-IU-2023:480-1 SUSE Image security@suse.de SUSE Security Team SUSE Image SUSE-IU-2023:480-1 Interim 1 1 2023-10-18T06:27:54Z current 2023-07-04T01:00:00Z 2023-07-04T01:00:00Z cve-database/bin/generate-cvrf-publiccloud.pl 2021-02-18T01:00:00Z Image update for SUSE-IU-2023:480-1 / google/sles-15-sp5-chost-byos-v20230704-arm64 This image update for google/sles-15-sp5-chost-byos-v20230704-arm64 contains the following changes: Package bind was updated: - Update to release 9.16.42 Security Fixes: * The overmem cleaning process has been improved, to prevent the cache from significantly exceeding the configured max-cache-size limit. (CVE-2023-2828) * A query that prioritizes stale data over lookup triggers a fetch to refresh the stale data in cache. If the fetch is aborted for exceeding the recursion quota, it was possible for named to enter an infinite callback loop and crash due to stack overflow. This has been fixed. (CVE-2023-2911) Bug Fixes: * Previously, it was possible for a delegation from cache to be returned to the client after the stale-answer-client-timeout duration. This has been fixed. [bsc#1212544, bsc#1212567, jsc#SLE-24600] - Update to release 9.16.41 Bug Fixes: * When removing delegations from an opt-out range, empty-non-terminal NSEC3 records generated by those delegations were not cleaned up. This has been fixed. [jsc#SLE-24600] - Update to release 9.16.40 Bug Fixes: * Logfiles using timestamp-style suffixes were not always correctly removed when the number of files exceeded the limit set by versions. This has been fixed for configurations which do not explicitly specify a directory path as part of the file argument in the channel specification. * Performance of DNSSEC validation in zones with many DNSKEY records has been improved. - Update to release 9.16.39 Feature Changes: * libuv support for receiving multiple UDP messages in a single recvmmsg() system call has been tweaked several times between libuv versions 1.35.0 and 1.40.0; the current recommended libuv version is 1.40.0 or higher. New rules are now in effect for running with a different version of libuv than the one used at compilation time. These rules may trigger a fatal error at startup: - Building against or running with libuv versions 1.35.0 and 1.36.0 is now a fatal error. - Running with libuv version higher than 1.34.2 is now a fatal error when named is built against libuv version 1.34.2 or lower. - Running with libuv version higher than 1.39.0 is now a fatal error when named is built against libuv version 1.37.0, 1.38.0, 1.38.1, or 1.39.0. * This prevents the use of libuv versions that may trigger an assertion failure when receiving multiple UDP messages in a single system call. Bug Fixes: * named could crash with an assertion failure when adding a new zone into the configuration file for a name which was already configured as a member zone for a catalog zone. This has been fixed. * When named starts up, it sends a query for the DNSSEC key for each configured trust anchor to determine whether the key has changed. In some unusual cases, the query might depend on a zone for which the server is itself authoritative, and would have failed if it were sent before the zone was fully loaded. This has now been fixed by delaying the key queries until all zones have finished loading. [jsc#SLE-24600] Package containerd was updated: - Update to containerd v1.6.21 for Docker v23.0.6-ce. Upstream release notes: <https://github.com/containerd/containerd/releases/tag/v1.6.21> bsc#1211578 - Require a minimum Go version explicitly rather than using golang(API). Fixes the change for bsc#1210298. Package cpupower was updated: - Add Emerald Ridge Intel CPU model support: * jsc#PED-4393 intel-speed-select tool support for EMR A tools-power-turbostat-Introduce-support-for-EMR.patch A add_emerald_ridge_intel_family.patch * jsc#PED-4395 Add EMR CPU support to turbostat A tools-power-x86-intel-speed-select-Add-Emerald-Rapid-quirk.patch Package docker was updated: - Update to Docker 23.0.6-ce. See upstream changelog online at <https://docs.docker.com/engine/release-notes/23.0/#2306>. bsc#1211578 - Rebase patches: * cli-0001-docs-include-required-tools-in-source-tree.patch - Re-unify packaging for SLE-12 and SLE-15. - Add patch to fix build on SLE-12 by switching back to libbtrfs-devel headers (the uapi headers in SLE-12 are too old). + 0003-BUILD-SLE12-revert-graphdriver-btrfs-use-kernel-UAPI.patch - Re-numbered patches: - 0003-bsc1073877-apparmor-clobber-docker-default-profile-o.patch + 0004-bsc1073877-apparmor-clobber-docker-default-profile-o.patch` - Update to Docker 23.0.5-ce. See upstream changelog online at <https://docs.docker.com/engine/release-notes/23.0/#2305>. - Rebase patches: * cli-0001-docs-include-required-tools-in-source-tree.patch - Update to Docker 23.0.4-ce. See upstream changelog online at <https://docs.docker.com/engine/release-notes/23.0/#2304>. bsc#1208074 - Rebase patches: * 0001-SECRETS-daemon-allow-directory-creation-in-run-secre.patch * 0002-SECRETS-SUSE-implement-SUSE-container-secrets.patch * 0003-bsc1073877-apparmor-clobber-docker-default-profile-o.patch - Renumbered patches: - 0004-bsc1073877-apparmor-clobber-docker-default-profile-o.patch - Remove upstreamed patches: - 0005-bsc1183855-btrfs-Do-not-disable-quota-on-cleanup.patch - 0006-bsc1193930-vendor-update-golang.org-x-crypto.patch - 0007-bsc1200022-fifo.Close-prevent-possible-panic-if-fifo.patch - Backport <https://github.com/docker/cli/pull/4228> to allow man pages to be built without internet access in OBS. + cli-0001-docs-include-required-tools-in-source-tree.patch Package dracut was updated: - Update to version 055+suse.366.g14047665: * fix(dracut-install): continue parsing if ldd prints "cannot execute binary file" (bsc#1212662) Package hwdata was updated: - update to 0.371: * Update pci, usb and vendor ids - update to 0.370: * Update pci, usb and vendor ids - update to 0.369: * Update pci, usb and vendor ids Package libcap was updated: - Fixed improper memory release in libcap/psx/psx.c:__wrap_pthread_create() (bsc#1211418 / CVE-2023-2602) CVE-2023-2602.patch - Fixed integer overflow or wraparound in libcap/cap_alloc.c:_libcap_strdup() (bsc#1211419 / CVE-2023-2603) CVE-2023-2603.patch Package gcc12 was updated: - Update to GCC 12.3 release, 0c61aa720e62f1baf0bfd178e283, git1204 * includes regression bug fixes - Add gcc12-testsuite-fixes.patch to pick testsuite related fixes from the branch after the release. - Speed up builds with --enable-link-serialization. - Update to gcc-12 branch head, 193f7e62815b4089dfaed4c2bd3, git749 - Don't rely on %usrmerged, set it based on standard %suse_version - Update to gcc-12 branch head, e4b5fec75aa8d0d01f6e042ec28, git696 * remove gcc12-fifo-jobserver-support.patch which is now included upstream - avoid trailing backslashes at the end of post install scripts - Update to gcc-12 branch head, 0aaef83351473e8f4eb774f8f99, git537 - Update embedded newlib to version 4.2.0 * includes newlib-4.1.0-aligned_alloc.patch - add gcc12-riscv-inline-atomics.patch, gcc12-riscv-pthread.patch: handle subword size inline atomics (needed by several openSUSE packages) Package openssl-1_1 was updated: - Security Fix: [bsc#1207534, CVE-2022-4304] * Reworked the Fix for the Timing Oracle in RSA Decryption The previous fix for this timing side channel turned out to cause a severe 2-3x performance regression in the typical use case compared to 1.1.1s. * Add openssl-CVE-2022-4304.patch * Removed patches: - openssl-CVE-2022-4304-1of2.patch - openssl-CVE-2022-4304-2of2.patch * Refreshed patches: - openssl-CVE-2023-0464.patch - openssl-CVE-2023-0465.patch - Update further expiring certificates that affect tests [bsc#1201627] * Add openssl-Update-further-expiring-certificates.patch - Security Fix: [CVE-2023-2650, bsc#1211430] * Possible DoS translating ASN.1 object identifiers * Add openssl-CVE-2023-2650.patch Package libzypp was updated: - build: honor libproxy.pc's includedir (bsc#1212222)- Curl: trim all custom headers (bsc#1212187) HTTP/2 RFC 9113 forbids fields ending with a space. So we make sure all custom headers are trimmed. This also includes headers returned by URL-Resolver plugins. - version 17.31.14 (22) Package runc was updated: - Update to runc v1.1.7. Upstream changelog is available from <https://github.com/opencontainers/runc/releases/tag/v1.1.7>. - Update runc.keyring to upstream version. - Update to runc v1.1.6. Upstream changelog is available from <https://github.com/opencontainers/runc/releases/tag/v1.1.6>. Package 000release-packages:sle-module-basesystem-release was updated: Package 000release-packages:sle-module-containers-release was updated: Package 000release-packages:sle-module-public-cloud-release was updated: Package 000release-packages:sle-module-server-applications-release was updated: Package 000release-packages:SLES-release was updated: Package suseconnect-ng was updated: - Update to version 1.1.0~git2.f42b4b2a060e: * Keep keepalive timer states when replacing SUSEConnect (bsc#1211588) Package wicked was updated: - extensions/nbft: add post-up script (bsc#1211647) In multipath scenarios, not all NBFT interfaces and respective connections may have been brought up during initramfs processing. If wicked brings up some NBFT interfaces after switching to the root file system, run a post-up script to initiate the NVMe connections. [+ 0002-extensions-nbft-add-post-up-script.bsc-1211647.patch] - bond: workaround 6.1 kernel enslave regression (boo#1206674) The kernel bond enslave rtnetlink message processing changed breaking an `ip link set down master bond0 dev eth0` like enslave which worked with all kernels from 4.12 up to 6.0. [+ 0001-bond-workaround-6.1-enslave-regression-boo-1206674.patch] Package zypper was updated: - targetos: Add an error note if XPath:/product/register/target is not defined in /etc/products.d/baseproduct (bsc#1211261) - targetos: Update help and man page (bsc#1211261) - version 1.14.61 The CVRF data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0). https://publiccloudimagechangeinfo.suse.com/google/sles-15-sp5-chost-byos-v20230704-arm64/ Public Cloud Image Info https://www.suse.com/support/security/rating/ SUSE Security Ratings Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64 bind-utils-9.16.42-150400.5.27.1 containerd-1.6.21-150000.93.1 containerd-ctr-1.6.21-150000.93.1 cpupower-5.14-150500.9.3.1 docker-23.0.6_ce-150000.178.1 dracut-055+suse.366.g14047665-150500.3.6.1 dracut-mkinitrd-deprecated-055+suse.366.g14047665-150500.3.6.1 hwdata-0.371-150000.3.62.1 libcap2-2.63-150400.3.3.1 libcpupower0-5.14-150500.9.3.1 libgcc_s1-12.3.0+git1204-150000.1.10.1 libopenssl1_1-1.1.1l-150500.17.6.1 libprotobuf-lite20-3.9.2-150200.4.21.1 libstdc++6-12.3.0+git1204-150000.1.10.1 libzypp-17.31.14-150400.3.35.1 openssl-1_1-1.1.1l-150500.17.6.1 python3-bind-9.16.42-150400.5.27.1 python3-ply-3.10-150000.3.3.4 runc-1.1.7-150000.46.1 suseconnect-ng-1.1.0~git2.f42b4b2a060e-150500.3.3.1 wicked-0.6.72-150500.3.7.1 wicked-service-0.6.72-150500.3.7.1 zypper-1.14.61-150400.3.24.1 bind-utils-9.16.42-150400.5.27.1 as a component of Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64 containerd-1.6.21-150000.93.1 as a component of Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64 containerd-ctr-1.6.21-150000.93.1 as a component of Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64 cpupower-5.14-150500.9.3.1 as a component of Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64 docker-23.0.6_ce-150000.178.1 as a component of Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64 dracut-055+suse.366.g14047665-150500.3.6.1 as a component of Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64 dracut-mkinitrd-deprecated-055+suse.366.g14047665-150500.3.6.1 as a component of Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64 hwdata-0.371-150000.3.62.1 as a component of Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64 libcap2-2.63-150400.3.3.1 as a component of Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64 libcpupower0-5.14-150500.9.3.1 as a component of Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64 libgcc_s1-12.3.0+git1204-150000.1.10.1 as a component of Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64 libopenssl1_1-1.1.1l-150500.17.6.1 as a component of Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64 libprotobuf-lite20-3.9.2-150200.4.21.1 as a component of Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64 libstdc++6-12.3.0+git1204-150000.1.10.1 as a component of Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64 libzypp-17.31.14-150400.3.35.1 as a component of Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64 openssl-1_1-1.1.1l-150500.17.6.1 as a component of Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64 python3-bind-9.16.42-150400.5.27.1 as a component of Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64 python3-ply-3.10-150000.3.3.4 as a component of Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64 runc-1.1.7-150000.46.1 as a component of Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64 suseconnect-ng-1.1.0~git2.f42b4b2a060e-150500.3.3.1 as a component of Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64 wicked-0.6.72-150500.3.7.1 as a component of Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64 wicked-service-0.6.72-150500.3.7.1 as a component of Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64 zypper-1.14.61-150400.3.24.1 as a component of Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64 A timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful decryption an attacker would have to be able to send a very large number of trial messages for decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE. For example, in a TLS connection, RSA is commonly used by a client to send an encrypted pre-master secret to the server. An attacker that had observed a genuine connection between a client and a server could use this flaw to send trial messages to the server and record the time taken to process them. After a sufficiently large number of messages the attacker could recover the pre-master secret used for the original connection and thus be able to decrypt the application data sent over that connection. CVE-2022-4304 Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64:libopenssl1_1-1.1.1l-150500.17.6.1 Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64:openssl-1_1-1.1.1l-150500.17.6.1 moderate A security vulnerability has been identified in all supported versions of OpenSSL related to the verification of X.509 certificate chains that include policy constraints. Attackers may be able to exploit this vulnerability by creating a malicious certificate chain that triggers exponential use of computational resources, leading to a denial-of-service (DoS) attack on affected systems. Policy processing is disabled by default but can be enabled by passing the `-policy' argument to the command line utilities or by calling the `X509_VERIFY_PARAM_set1_policies()' function. CVE-2023-0464 Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64:libopenssl1_1-1.1.1l-150500.17.6.1 Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64:openssl-1_1-1.1.1l-150500.17.6.1 moderate Applications that use a non-default option when verifying certificates may be vulnerable to an attack from a malicious CA to circumvent certain checks. Invalid certificate policies in leaf certificates are silently ignored by OpenSSL and other certificate policy checks are skipped for that certificate. A malicious CA could use this to deliberately assert invalid certificate policies in order to circumvent policy checking on the certificate altogether. Policy processing is disabled by default but can be enabled by passing the `-policy' argument to the command line utilities or by calling the `X509_VERIFY_PARAM_set1_policies()' function. CVE-2023-0465 Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64:libopenssl1_1-1.1.1l-150500.17.6.1 Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64:openssl-1_1-1.1.1l-150500.17.6.1 moderate A vulnerability was found in the pthread_create() function in libcap. This issue may allow a malicious actor to use cause __real_pthread_create() to return an error, which can exhaust the process memory. CVE-2023-2602 Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64:libcap2-2.63-150400.3.3.1 low A vulnerability was found in libcap. This issue occurs in the _libcap_strdup() function and can lead to an integer overflow if the input string is close to 4GiB. CVE-2023-2603 Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64:libcap2-2.63-150400.3.3.1 moderate Issue summary: Processing some specially crafted ASN.1 object identifiers or data containing them may be very slow. Impact summary: Applications that use OBJ_obj2txt() directly, or use any of the OpenSSL subsystems OCSP, PKCS7/SMIME, CMS, CMP/CRMF or TS with no message size limit may experience notable to very long delays when processing those messages, which may lead to a Denial of Service. An OBJECT IDENTIFIER is composed of a series of numbers - sub-identifiers - most of which have no size limit. OBJ_obj2txt() may be used to translate an ASN.1 OBJECT IDENTIFIER given in DER encoding form (using the OpenSSL type ASN1_OBJECT) to its canonical numeric text form, which are the sub-identifiers of the OBJECT IDENTIFIER in decimal form, separated by periods. When one of the sub-identifiers in the OBJECT IDENTIFIER is very large (these are sizes that are seen as absurdly large, taking up tens or hundreds of KiBs), the translation to a decimal number in text may take a very long time. The time complexity is O(n^2) with 'n' being the size of the sub-identifiers in bytes (*). With OpenSSL 3.0, support to fetch cryptographic algorithms using names / identifiers in string form was introduced. This includes using OBJECT IDENTIFIERs in canonical numeric text form as identifiers for fetching algorithms. Such OBJECT IDENTIFIERs may be received through the ASN.1 structure AlgorithmIdentifier, which is commonly used in multiple protocols to specify what cryptographic algorithm should be used to sign or verify, encrypt or decrypt, or digest passed data. Applications that call OBJ_obj2txt() directly with untrusted data are affected, with any version of OpenSSL. If the use is for the mere purpose of display, the severity is considered low. In OpenSSL 3.0 and newer, this affects the subsystems OCSP, PKCS7/SMIME, CMS, CMP/CRMF or TS. It also impacts anything that processes X.509 certificates, including simple things like verifying its signature. The impact on TLS is relatively low, because all versions of OpenSSL have a 100KiB limit on the peer's certificate chain. Additionally, this only impacts clients, or servers that have explicitly enabled client authentication. In OpenSSL 1.1.1 and 1.0.2, this only affects displaying diverse objects, such as X.509 certificates. This is assumed to not happen in such a way that it would cause a Denial of Service, so these versions are considered not affected by this issue in such a way that it would be cause for concern, and the severity is therefore considered low. CVE-2023-2650 Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64:libopenssl1_1-1.1.1l-150500.17.6.1 Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64:openssl-1_1-1.1.1l-150500.17.6.1 moderate Every `named` instance configured to run as a recursive resolver maintains a cache database holding the responses to the queries it has recently sent to authoritative servers. The size limit for that cache database can be configured using the `max-cache-size` statement in the configuration file; it defaults to 90% of the total amount of memory available on the host. When the size of the cache reaches 7/8 of the configured limit, a cache-cleaning algorithm starts to remove expired and/or least-recently used RRsets from the cache, to keep memory use below the configured limit. It has been discovered that the effectiveness of the cache-cleaning algorithm used in `named` can be severely diminished by querying the resolver for specific RRsets in a certain order, effectively allowing the configured `max-cache-size` limit to be significantly exceeded. This issue affects BIND 9 versions 9.11.0 through 9.16.41, 9.18.0 through 9.18.15, 9.19.0 through 9.19.13, 9.11.3-S1 through 9.16.41-S1, and 9.18.11-S1 through 9.18.15-S1. CVE-2023-2828 Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64:bind-utils-9.16.42-150400.5.27.1 Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64:python3-bind-9.16.42-150400.5.27.1 important If the `recursive-clients` quota is reached on a BIND 9 resolver configured with both `stale-answer-enable yes;` and `stale-answer-client-timeout 0;`, a sequence of serve-stale-related lookups could cause `named` to loop and terminate unexpectedly due to a stack overflow. This issue affects BIND 9 versions 9.16.33 through 9.16.41, 9.18.7 through 9.18.15, 9.16.33-S1 through 9.16.41-S1, and 9.18.11-S1 through 9.18.15-S1. CVE-2023-2911 Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64:bind-utils-9.16.42-150400.5.27.1 Public Cloud Image google/sles-15-sp5-chost-byos-v20230704-arm64:python3-bind-9.16.42-150400.5.27.1 important