Описание
Security update for openssl-3
This update for openssl-3 fixes the following issues:
Security issues fixed:
- CVE-2024-4603: Check DSA parameters for excessive sizes before validating (bsc#1224388)
- CVE-2024-4741: Fixed a use-after-free with SSL_free_buffers. (bsc#1225551)
Other issues fixed:
- Enable livepatching support (bsc#1223428)
- Fix HDKF key derivation (bsc#1225291, gh#openssl/openssl#23448, + gh#openssl/openssl#23456)
Список пакетов
Container bci/bci-init:latest
Container bci/bci-sle15-kernel-module-devel:latest
Container bci/gcc:latest
Container bci/golang:1.22-openssl
Container bci/golang:1.23
Container bci/golang:latest
Container bci/kiwi:latest
Container bci/node:22
Container bci/nodejs:latest
Container bci/openjdk-devel:17
Container bci/openjdk-devel:latest
Container bci/openjdk:17
Container bci/openjdk:latest
Container bci/php-apache:latest
Container bci/php-fpm:latest
Container bci/php:latest
Container bci/python:3
Container bci/python:latest
Container bci/ruby:latest
Container bci/rust:1.84
Container bci/rust:latest
Container bci/spack:latest
Container containers/apache-pulsar:3.3
Container containers/apache-tomcat:10.1-openjdk11
Container containers/apache-tomcat:10.1-openjdk17
Container containers/apache-tomcat:10.1-openjdk21
Container containers/apache-tomcat:9-openjdk11
Container containers/apache-tomcat:9-openjdk17
Container containers/apache-tomcat:9-openjdk21
Container containers/apache-tomcat:9-openjdk8
Container containers/milvus:2.4
Container containers/ollama:0
Container containers/open-webui:0
Container containers/python:3.11
Container containers/python:3.9
Container containers/pytorch:2-nvidia
Container containers/pytorch:2.5.0
Container suse/389-ds:latest
Container suse/git:latest
Container suse/helm:latest
Container suse/hpc/warewulf4-x86_64/sle-hpc-node:latest
Container suse/manager/5.0/x86_64/proxy-httpd:latest
Container suse/manager/5.0/x86_64/proxy-salt-broker:latest
Container suse/manager/5.0/x86_64/proxy-squid:latest
Container suse/manager/5.0/x86_64/proxy-ssh:latest
Container suse/manager/5.0/x86_64/proxy-tftpd:latest
Container suse/manager/5.0/x86_64/server-attestation:latest
Container suse/manager/5.0/x86_64/server-hub-xmlrpc-api:latest
Container suse/manager/5.0/x86_64/server-migration-14-16:latest
Container suse/manager/5.0/x86_64/server:latest
Container suse/mariadb-client:latest
Container suse/mariadb:latest
Container suse/nginx:latest
Container suse/pcp:latest
Container suse/postgres:16
Container suse/postgres:latest
Container suse/registry:latest
Container suse/rmt-server:latest
Container suse/sle15:15.6
Container suse/stunnel:latest
Container trento/trento-wanda:latest
Container trento/trento-web:latest
Image SLES15-SP6
Image SLES15-SP6-Azure-Basic
Image SLES15-SP6-Azure-Standard
Image SLES15-SP6-BYOS
Image SLES15-SP6-BYOS-Azure
Image SLES15-SP6-BYOS-EC2
Image SLES15-SP6-BYOS-GCE
Image SLES15-SP6-CHOST-BYOS
Image SLES15-SP6-CHOST-BYOS-Aliyun
Image SLES15-SP6-CHOST-BYOS-Azure
Image SLES15-SP6-CHOST-BYOS-EC2
Image SLES15-SP6-CHOST-BYOS-GCE
Image SLES15-SP6-CHOST-BYOS-GDC
Image SLES15-SP6-CHOST-BYOS-SAP-CCloud
Image SLES15-SP6-EC2
Image SLES15-SP6-EC2-ECS-HVM
Image SLES15-SP6-GCE
Image SLES15-SP6-HPC
Image SLES15-SP6-HPC-Azure
Image SLES15-SP6-HPC-BYOS
Image SLES15-SP6-HPC-BYOS-Azure
Image SLES15-SP6-HPC-BYOS-EC2
Image SLES15-SP6-HPC-BYOS-GCE
Image SLES15-SP6-HPC-EC2
Image SLES15-SP6-HPC-GCE
Image SLES15-SP6-Hardened-BYOS
Image SLES15-SP6-Hardened-BYOS-Azure
Image SLES15-SP6-Hardened-BYOS-EC2
Image SLES15-SP6-Hardened-BYOS-GCE
Image SLES15-SP6-SAP
Image SLES15-SP6-SAP-Azure
Image SLES15-SP6-SAP-Azure-LI-BYOS
Image SLES15-SP6-SAP-Azure-LI-BYOS-Production
Image SLES15-SP6-SAP-Azure-VLI-BYOS
Image SLES15-SP6-SAP-Azure-VLI-BYOS-Production
Image SLES15-SP6-SAP-BYOS
Image SLES15-SP6-SAP-BYOS-Azure
Image SLES15-SP6-SAP-BYOS-EC2
Image SLES15-SP6-SAP-BYOS-GCE
Image SLES15-SP6-SAP-EC2
Image SLES15-SP6-SAP-GCE
Image SLES15-SP6-SAP-Hardened
Image SLES15-SP6-SAP-Hardened-Azure
Image SLES15-SP6-SAP-Hardened-BYOS
Image SLES15-SP6-SAP-Hardened-BYOS-Azure
Image SLES15-SP6-SAP-Hardened-BYOS-EC2
Image SLES15-SP6-SAP-Hardened-BYOS-GCE
Image SLES15-SP6-SAP-Hardened-EC2
Image SLES15-SP6-SAP-Hardened-GCE
Image SLES15-SP6-SAPCAL
Image SLES15-SP6-SAPCAL-Azure
Image SLES15-SP6-SAPCAL-EC2
Image SLES15-SP6-SAPCAL-GCE
Image ai_15_6
Image python_15_6
Image tomcat_15_6
SUSE Linux Enterprise Module for Basesystem 15 SP6
openSUSE Leap 15.6
Ссылки
- Link for SUSE-SU-2024:2066-1
- E-Mail link for SUSE-SU-2024:2066-1
- SUSE Security Ratings
- SUSE Bug 1223428
- SUSE Bug 1224388
- SUSE Bug 1225291
- SUSE Bug 1225551
- SUSE CVE CVE-2024-4603 page
- SUSE CVE CVE-2024-4741 page
Описание
Issue summary: Checking excessively long DSA keys or parameters may be very slow. Impact summary: Applications that use the functions EVP_PKEY_param_check() or EVP_PKEY_public_check() to check a DSA public key or DSA parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service. The functions EVP_PKEY_param_check() or EVP_PKEY_public_check() perform various checks on DSA parameters. Some of those computations take a long time if the modulus (`p` parameter) is too large. Trying to use a very large modulus is slow and OpenSSL will not allow using public keys with a modulus which is over 10,000 bits in length for signature verification. However the key and parameter check functions do not limit the modulus size when performing the checks. An application that calls EVP_PKEY_param_check() or EVP_PKEY_public_check() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack. These functions are not called by OpenSSL itself on untrusted DSA keys so only applications that directly call these functions may be vulnerable. Also vulnerable are the OpenSSL pkey and pkeyparam command line applications when using the `-check` option. The OpenSSL SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are affected by this issue.
Затронутые продукты
Ссылки
- CVE-2024-4603
- SUSE Bug 1224388
Описание
Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause memory to be accessed that was previously freed in some situations Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, only applications that directly call the SSL_free_buffers function are affected by this issue. Applications that do not call this function are not vulnerable. Our investigations indicate that this function is rarely used by applications. The SSL_free_buffers function is used to free the internal OpenSSL buffer used when processing an incoming record from the network. The call is only expected to succeed if the buffer is not currently in use. However, two scenarios have been identified where the buffer is freed even when still in use. The first scenario occurs where a record header has been received from the network and processed by OpenSSL, but the full record body has not yet arrived. In this case calling SSL_free_buffers will succeed even though a record has only been partially processed and the buffer is still in use. The second scenario occurs where a full record containing application data has been received and processed by OpenSSL but the application has only read part of this data. Again a call to SSL_free_buffers will succeed even though the buffer is still in use. While these scenarios could occur accidentally during normal operation a malicious attacker could attempt to engineer a stituation where this occurs. We are not aware of this issue being actively exploited. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
Затронутые продукты
Ссылки
- CVE-2024-4741
- SUSE Bug 1225551
- SUSE Bug 1225552