Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

suse-cvrf логотип

SUSE-SU-2026:3835-1

Опубликовано: 27 авг. 2026
Источник: suse-cvrf

Описание

Security update for openssl, openssl-3

This update for openssl, openssl-3 fixes the following issues:

OpenSSL is updated to 3.5.0 in SLE-15-SP7: (jsc#PED-16072)

  • Enables Post-Quantum Cryptography (PQC) TLS support

Security issues fixed:

  • CVE-2026-42764: NULL pointer dereference in QUIC server initial packet handling (bsc#1266347)
  • CVE-2026-34182: CMS AuthEnvelopedData Processing May Accept Forged Messages (bsc#1266344)
  • CVE-2026-28390: NULL pointer dereference during processing of a crafted CMS EnvelopedData message with KeyTransportRecipientInfo (bsc#1261678)
  • CVE-2026-2673: TLS 1.3 servers may choose unexpected key agreement group (bsc#1259652)
  • CVE-2025-66199: TLS 1.3 CompressedCertificate excessive memory allocation (bsc#1256833)
  • CVE-2025-15469: 'openssl dgst' one-shot codepath silently truncates inputs greater than 16MB (bsc#1256832)
  • CVE-2025-11187: Improper validation of PBMAC1 parameters in PKCS#12 MAC verification (bsc#1256829)
  • CVE-2025-15468: NULL dereference in SSL_CIPHER_find() function on unknown cipher ID (bsc#1256831)
  • CVE-2025-9231: Fix timing side-channel in SM2 algorithm on 64 bit ARM (bsc#1250233)
  • CVE-2025-9232: Fix out-of-bounds read in HTTP client no_proxy handling (bsc#1250234)
  • CVE-2025-4575: Fix the x509 application adding trusted use instead of rejected use (bsc#1243564)
  • CVE-2025-27587: Minerva side channel vulnerability in P-384 (bsc#1243459)
  • CVE-2024-12797: Fixed RFC7250 handshakes with unauthenticated servers don't abort as expected. (bsc#1236599)
  • CVE-2024-13176: Fixed timing side-channel in ECDSA signature computation.
  • CVE-2024-9143: Fixed possible OOB memory access with invalid low-level GF(2^m) elliptic curve parameters.
  • CVE-2024-13176: Fix timing side-channel in ECDSA signature computation (bsc#1236136)

POWER performance enhancements:

  • Optimized MLDSA NTT, supports p8 and above architectures (jsc#PED-14569)
  • Adapt spec file for immutability via systemd-tmpfiles (jsc#PED-14813)

  • Fix check %{suse_version} > 1600 (jsc#PED-15816)

  • Fix NULL pointer dereference when processing an OCSP response

  • Remove showciphers.c in favor of openssl ciphers

  • Use %ldconfig_scriptlets

  • Enable livepatching support for ppc64le [bsc#1257274]

  • Move ssl configuration files to the libopenssl package [bsc#1247463]

  • Don't install unneeded NOTES

  • Disable LTO for userspace livepatching [jsc#PED-13245]

  • Fix P-384 curve on lower-than-P9 PPC64 targets [bsc#1243014]

  • FIPS: Fix the speed command in FIPS mode for KMAC

  • FIPS: Restore the check to deny SHA1 signatures in FIPS mode and the functionality to allow/deny via crypto-policies. [jsc#PED-12224]

Update to 3.5.0:

  • Changes:

    • Default encryption cipher for the req, cms, and smime applications changed from des-ede3-cbc to aes-256-cbc.
    • The default TLS supported groups list has been changed to include and prefer hybrid PQC KEM groups. Some practically unused groups were removed from the default list.
    • The default TLS keyshares have been changed to offer X25519MLKEM768 and and X25519.
    • All BIO_meth_get_*() functions were deprecated.
    • New features:

      • Support for server side QUIC (RFC 9000)
      • Support for 3rd party QUIC stacks including 0-RTT support
      • Support for PQC algorithms (ML-KEM, ML-DSA and SLH-DSA)
      • A new configuration option no-tls-deprecated-ec to disable support for TLS groups deprecated in RFC8422
      • A new configuration option enable-fips-jitter to make the FIPS provider to use the JITTER seed source
      • Support for central key generation in CMP
      • Support added for opaque symmetric key objects (EVP_SKEY)
      • Support for multiple TLS keyshares and improved TLS key establishment group configurability
      • API support for pipelining in provided cipher algorithms

Changes between 3.3.0 and 3.4.0:

  • Changes:

    • Deprecation of TS_VERIFY_CTX_set_* functions and addition of replacement TS_VERIFY_CTX_set0_* functions with improved semantics
    • The X25519 and X448 key exchange implementation in the FIPS provider is unapproved and has fips=no property.
    • SHAKE-128 and SHAKE-256 implementations have no default digest length anymore. That means these algorithms cannot be used with EVP_DigestFinal/_ex() unless the xoflen param is set before.
    • Setting config_diagnostics=1 in the config file will cause errors to be returned from SSL_CTX_new() and SSL_CTX_new_ex() if there is an error in the ssl module configuration.
    • An empty renegotiate extension will be used in TLS client hellos instead of the empty renegotiation SCSV, for all connections with a minimum TLS version > 1.0.
    • Deprecation of SSL_SESSION_get_time(), SSL_SESSION_set_time() and SSL_CTX_flush_sessions() functions in favor of their respective _ex functions which are Y2038-safe on platforms with Y2038-safe time_t
  • New features:

    • Support for directly fetched composite signature algorithms such as RSA-SHA2-256 including new API functions
    • FIPS indicators support in the FIPS provider and various updates of the FIPS provider required for future FIPS 140-3 validations
    • Implementation of RFC 9579 (PBMAC1) in PKCS#12
    • An optional additional random seed source RNG JITTER using a statically linked jitterentropy library
    • New options -not_before and -not_after for explicit setting start and end dates of certificates created with the req and x509 apps
    • Support for integrity-only cipher suites TLS_SHA256_SHA256 and TLS_SHA384_SHA384 in TLS 1.3, as defined in RFC 9150
    • Support for retrieving certificate request templates and CRLs in CMP
    • Support for additional X.509v3 extensions related to Attribute Certificates
    • Initial Attribute Certificate (RFC 5755) support
    • Possibility to customize ECC groups initialization to use precomputed values to save CPU time and use of this feature by the P-256 implementation

Changes between 3.2.0 and 3.3.0:

  • Changes:

    • Optimized AES-CTR for ARM Neoverse V1 and V2
    • Various optimizations for cryptographic routines using RISC-V vector crypto extensions
    • Added assembly implementation for md5 on loongarch64
    • Accept longer context for TLS 1.2 exporters
    • The activate and soft_load configuration settings for providers in openssl.cnf have been updated to require a value of [1|yes|true|on] (in lower or UPPER case) to enable the setting. Conversely a value of [0|no|false|off] will disable the setting.
    • In openssl speed, changed the default hash function used with hmac from md5 to sha256.
    • The -verify option to the openssl crl and openssl req will make the program exit with 1 on failure.
    • The d2i_ASN1_GENERALIZEDTIME(), d2i_ASN1_UTCTIME(), ASN1_TIME_check(), and related functions have been augmented to check for a minimum length of the input string, in accordance with ITU-T X.690 section 11.7 and 11.8.
    • OPENSSL_sk_push() and sk__push() functions now return 0 instead of -1 if called with a NULL stack argument.
    • New limit on HTTP response headers is introduced to HTTP client. The default limit is set to 256 header lines.
  • Bug fixes and mitigations:

    • The BIO_get_new_index() function can only be called 127 times before it reaches its upper bound of BIO_TYPE_MASK and will now return -1 once its exhausted.
  • new features:

    • Support for qlog for tracing QUIC connections has been added
    • Added APIs to allow configuring the negotiated idle timeout for QUIC connections, and to allow determining the number of additional streams that can currently be created for a QUIC connection.
    • Added APIs to allow disabling implicit QUIC event processing for QUIC SSL objects
    • Added APIs to allow querying the size and utilisation of a QUIC stream's write buffer
    • New API SSL_write_ex2, which can be used to send an end-of-stream (FIN) condition in an optimised way when using QUIC.
    • Limited support for polling of QUIC connection and stream objects in a non-blocking manner.
    • Added a new EVP_DigestSqueeze() API. This allows SHAKE to squeeze multiple times with different output sizes.
    • The BLAKE2s hash algorithm matches BLAKE2b's support for configurable output length.
    • The EVP_PKEY_fromdata function has been augmented to allow for the derivation of CRT (Chinese Remainder Theorem) parameters when requested
    • Added API functions SSL_SESSION_get_time_ex(), SSL_SESSION_set_time_ex() using time_t which is Y2038 safe on 32 bit systems when 64 bit time is enabled.
    • Unknown entries in TLS SignatureAlgorithms, ClientSignatureAlgorithms config options and the respective calls to SSL[_CTX]_set1_sigalgs() and SSL[_CTX]_set1_client_sigalgs() that start with ? character are ignored and the configuration will still be used.
    • Added -set_issuer and -set_subject options to openssl x509 to override the Issuer and Subject when creating a certificate. The -subj option now is an alias for -set_subject.
    • Added several new features of CMPv3 defined in RFC 9480 and RFC 9483
    • New option SSL_OP_PREFER_NO_DHE_KEX, which allows configuring a TLS1.3 server to prefer session resumption using PSK-only key exchange over PSK with DHE, if both are available.
    • New atexit configuration switch, which controls whether the OPENSSL_cleanup is registered when libcrypto is unloaded.
    • Added X509_STORE_get1_objects to avoid issues with the existing X509_STORE_get0_objects API in multi-threaded applications.
    • Support for using certificate profiles and extened delayed delivery in CMP
  • FIPS: Mark SHA-1 as non-approved in the SLI. [jsc#PED-12224]

  • Introduce --without lto. When %{optflags} contains -flto=, tests cases are also built using -flto= which significantly increases build times, this option disables lto which improve iteration times when developing.

Update to 3.2.4:

  • Remove the engines' directories and symlinks that were added to allow parallel installations with openssl-1_1.
  • Add ktls capability [bsc#1216950]

Список пакетов

Container bci/bci-base-fips:latest
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl3-3.5.0-150700.5.45.2
Container bci/bci-init:latest
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl3-3.5.0-150700.5.45.2
Container bci/bci-micro-fips:latest
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl3-3.5.0-150700.5.45.2
Container bci/bci-sle15-kernel-module-devel:latest
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl3-3.5.0-150700.5.45.2
openssl-3.5.0-150700.3.4.1
openssl-3-3.5.0-150700.5.45.2
Container bci/dotnet-aspnet:8.0
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl3-3.5.0-150700.5.45.2
Container bci/dotnet-aspnet:9.0
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl3-3.5.0-150700.5.45.2
Container bci/dotnet-aspnet:latest
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl3-3.5.0-150700.5.45.2
Container bci/dotnet-runtime:8.0
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl3-3.5.0-150700.5.45.2
Container bci/dotnet-runtime:9.0
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl3-3.5.0-150700.5.45.2
Container bci/dotnet-runtime:latest
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl3-3.5.0-150700.5.45.2
Container bci/dotnet-sdk:8.0
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl3-3.5.0-150700.5.45.2
Container bci/dotnet-sdk:9.0
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl3-3.5.0-150700.5.45.2
Container bci/dotnet-sdk:latest
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl3-3.5.0-150700.5.45.2
Container bci/golang:1.25-openssl
libopenssl-3-devel-3.5.0-150700.5.45.2
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl3-3.5.0-150700.5.45.2
Container bci/golang:latest
libopenssl-3-devel-3.5.0-150700.5.45.2
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl3-3.5.0-150700.5.45.2
Container bci/node:22
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl3-3.5.0-150700.5.45.2
Container bci/openjdk-devel:17
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl3-3.5.0-150700.5.45.2
openssl-3.5.0-150700.3.4.1
openssl-3-3.5.0-150700.5.45.2
Container bci/openjdk-devel:21
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl3-3.5.0-150700.5.45.2
openssl-3.5.0-150700.3.4.1
openssl-3-3.5.0-150700.5.45.2
Container bci/openjdk-devel:latest
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl3-3.5.0-150700.5.45.2
openssl-3.5.0-150700.3.4.1
openssl-3-3.5.0-150700.5.45.2
Container bci/openjdk:17
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl3-3.5.0-150700.5.45.2
openssl-3.5.0-150700.3.4.1
openssl-3-3.5.0-150700.5.45.2
Container bci/openjdk:21
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl3-3.5.0-150700.5.45.2
openssl-3.5.0-150700.3.4.1
openssl-3-3.5.0-150700.5.45.2
Container bci/openjdk:latest
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl3-3.5.0-150700.5.45.2
openssl-3.5.0-150700.3.4.1
openssl-3-3.5.0-150700.5.45.2
Container bci/python:3
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl3-3.5.0-150700.5.45.2
openssl-3.5.0-150700.3.4.1
openssl-3-3.5.0-150700.5.45.2
Container bci/python:latest
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl3-3.5.0-150700.5.45.2
openssl-3.5.0-150700.3.4.1
openssl-3-3.5.0-150700.5.45.2
Container bci/ruby:2
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl3-3.5.0-150700.5.45.2
Container bci/ruby:latest
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl3-3.5.0-150700.5.45.2
Container bci/rust:1.96
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl3-3.5.0-150700.5.45.2
Container bci/rust:latest
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl3-3.5.0-150700.5.45.2
Container bci/spack:latest
libopenssl-3-devel-3.5.0-150700.5.45.2
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl-devel-3.5.0-150700.3.4.1
libopenssl3-3.5.0-150700.5.45.2
openssl-3.5.0-150700.3.4.1
openssl-3-3.5.0-150700.5.45.2
Container private-registry/1.2/harbor-core:latest
libopenssl3-3.5.0-150700.5.45.2
openssl-3.5.0-150700.3.4.1
openssl-3-3.5.0-150700.5.45.2
Container private-registry/1.2/harbor-exporter:latest
libopenssl3-3.5.0-150700.5.45.2
openssl-3.5.0-150700.3.4.1
openssl-3-3.5.0-150700.5.45.2
Container private-registry/1.2/harbor-jobservice:latest
libopenssl3-3.5.0-150700.5.45.2
openssl-3.5.0-150700.3.4.1
openssl-3-3.5.0-150700.5.45.2
Container private-registry/1.2/harbor-portal:latest
libopenssl3-3.5.0-150700.5.45.2
Container private-registry/1.2/harbor-registry:latest
libopenssl3-3.5.0-150700.5.45.2
openssl-3.5.0-150700.3.4.1
openssl-3-3.5.0-150700.5.45.2
Container private-registry/1.2/harbor-registryctl:latest
libopenssl3-3.5.0-150700.5.45.2
openssl-3.5.0-150700.3.4.1
openssl-3-3.5.0-150700.5.45.2
Container private-registry/1.2/harbor-trivy-adapter:latest
libopenssl3-3.5.0-150700.5.45.2
openssl-3.5.0-150700.3.4.1
openssl-3-3.5.0-150700.5.45.2
Container private-registry/harbor-core:latest
libopenssl3-3.5.0-150700.5.45.2
openssl-3.5.0-150700.3.4.1
openssl-3-3.5.0-150700.5.45.2
Container private-registry/harbor-exporter:latest
libopenssl3-3.5.0-150700.5.45.2
openssl-3.5.0-150700.3.4.1
openssl-3-3.5.0-150700.5.45.2
Container private-registry/harbor-jobservice:latest
libopenssl3-3.5.0-150700.5.45.2
openssl-3.5.0-150700.3.4.1
openssl-3-3.5.0-150700.5.45.2
Container private-registry/harbor-portal:latest
libopenssl3-3.5.0-150700.5.45.2
Container private-registry/harbor-registry:latest
libopenssl3-3.5.0-150700.5.45.2
openssl-3.5.0-150700.3.4.1
openssl-3-3.5.0-150700.5.45.2
Container private-registry/harbor-registryctl:latest
libopenssl3-3.5.0-150700.5.45.2
openssl-3.5.0-150700.3.4.1
openssl-3-3.5.0-150700.5.45.2
Container private-registry/harbor-trivy-adapter:latest
libopenssl3-3.5.0-150700.5.45.2
openssl-3.5.0-150700.3.4.1
openssl-3-3.5.0-150700.5.45.2
Container suse/kea:2.6
libopenssl3-3.5.0-150700.5.45.2
Container suse/kiosk/firefox-esr:latest
libopenssl3-3.5.0-150700.5.45.2
Container suse/kiosk/pulseaudio:latest
libopenssl3-3.5.0-150700.5.45.2
Container suse/kiosk/tigervnc-x11vnc:latest
libopenssl3-3.5.0-150700.5.45.2
openssl-3.5.0-150700.3.4.1
openssl-3-3.5.0-150700.5.45.2
Container suse/kiosk/xorg-client:latest
libopenssl3-3.5.0-150700.5.45.2
Container suse/kiosk/xorg:latest
libopenssl3-3.5.0-150700.5.45.2
Container suse/mariadb-client:latest
libopenssl3-3.5.0-150700.5.45.2
Container suse/mariadb:latest
libopenssl3-3.5.0-150700.5.45.2
openssl-3.5.0-150700.3.4.1
openssl-3-3.5.0-150700.5.45.2
Container suse/postgres:16
libopenssl3-3.5.0-150700.5.45.2
Container suse/postgres:16.15
libopenssl3-3.5.0-150700.5.45.2
Container suse/postgres:17
libopenssl3-3.5.0-150700.5.45.2
Container suse/postgres:17.10
libopenssl3-3.5.0-150700.5.45.2
Container suse/postgres:latest
libopenssl3-3.5.0-150700.5.45.2
Container suse/rmt-server:latest
libopenssl3-3.5.0-150700.5.45.2
Container suse/samba-client:latest
libopenssl3-3.5.0-150700.5.45.2
Container suse/samba-server:latest
libopenssl3-3.5.0-150700.5.45.2
Container suse/samba-toolbox:latest
libopenssl3-3.5.0-150700.5.45.2
Container suse/sle15:latest
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl3-3.5.0-150700.5.45.2
openssl-3.5.0-150700.3.4.1
openssl-3-3.5.0-150700.5.45.2
Container third-party/amd/amdgpu-driver:sles-15.7-30.20.1
libopenssl3-3.5.0-150700.5.45.2
Container third-party/amd/amdgpu-driver:sles-15.7-30.30.4
libopenssl3-3.5.0-150700.5.45.2
Container third-party/amd/amdgpu-driver:sles-15.7-31.10
libopenssl3-3.5.0-150700.5.45.2
Container third-party/amd/amdgpu-driver:sles-15.7-31.20
libopenssl3-3.5.0-150700.5.45.2
Container third-party/amd/amdgpu-driver:sles-15.7-31.30
libopenssl3-3.5.0-150700.5.45.2
Container third-party/amd/amdgpu-driver:sles-15.7-31.40.1
libopenssl3-3.5.0-150700.5.45.2
Container third-party/nvidia/driver:550-sles15.7
libopenssl3-3.5.0-150700.5.45.2
Container third-party/nvidia/driver:570-sles15.7
libopenssl3-3.5.0-150700.5.45.2
Container third-party/nvidia/driver:575-sles15.7
libopenssl3-3.5.0-150700.5.45.2
Container third-party/nvidia/driver:580-sles15.7
libopenssl3-3.5.0-150700.5.45.2
Container third-party/nvidia/driver:590-sles15.7
libopenssl3-3.5.0-150700.5.45.2
Container third-party/nvidia/driver:595-sles15.7
libopenssl3-3.5.0-150700.5.45.2
SUSE Linux Enterprise Module for Basesystem 15 SP7
libopenssl-3-devel-3.5.0-150700.5.45.2
libopenssl-3-fips-provider-3.5.0-150700.5.45.2
libopenssl-3-fips-provider-32bit-3.5.0-150700.5.45.2
libopenssl-devel-3.5.0-150700.3.4.1
libopenssl-fips-provider-3.5.0-150700.3.4.1
libopenssl3-3.5.0-150700.5.45.2
libopenssl3-32bit-3.5.0-150700.5.45.2
openssl-3.5.0-150700.3.4.1
openssl-3-3.5.0-150700.5.45.2
SUSE Linux Enterprise Module for Web and Scripting 15 SP7
nodejs24-24.18.1-150700.15.18.1
nodejs24-devel-24.18.1-150700.15.18.1
nodejs24-docs-24.18.1-150700.15.18.1
npm24-24.18.1-150700.15.18.1

Описание

Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server may fail to notice that the server was not authenticated, because handshakes don't abort as expected when the SSL_VERIFY_PEER verification mode is set. Impact summary: TLS and DTLS connections using raw public keys may be vulnerable to man-in-middle attacks when server authentication failure is not detected by clients. RPKs are disabled by default in both TLS clients and TLS servers. The issue only arises when TLS clients explicitly enable RPK use by the server, and the server, likewise, enables sending of an RPK instead of an X.509 certificate chain. The affected clients are those that then rely on the handshake to fail when the server's RPK fails to match one of the expected public keys, by setting the verification mode to SSL_VERIFY_PEER. Clients that enable server-side raw public keys can still find out that raw public key verification failed by calling SSL_get_verify_result(), and those that do, and take appropriate action, are not affected. This issue was introduced in the initial implementation of RPK support in OpenSSL 3.2. The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.


Затронутые продукты
Container bci/bci-base-fips:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-base-fips:latest:libopenssl3-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl3-3.5.0-150700.5.45.2

Ссылки

Описание

Issue summary: A timing side-channel which could potentially allow recovering the private key exists in the ECDSA signature computation. Impact summary: A timing side-channel in ECDSA signature computations could allow recovering the private key by an attacker. However, measuring the timing would require either local access to the signing application or a very fast network connection with low latency. There is a timing signal of around 300 nanoseconds when the top word of the inverted ECDSA nonce value is zero. This can happen with significant probability only for some of the supported elliptic curves. In particular the NIST P-521 curve is affected. To be able to measure this leak, the attacker process must either be located in the same physical computer or must have a very fast network connection with low latency. For that reason the severity of this vulnerability is Low. The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are affected by this issue.


Затронутые продукты
Container bci/bci-base-fips:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-base-fips:latest:libopenssl3-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl3-3.5.0-150700.5.45.2

Ссылки

Описание

Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the field polynomial can lead to out-of-bounds memory reads or writes. Impact summary: Out of bound memory writes can lead to an application crash or even a possibility of a remote code execution, however, in all the protocols involving Elliptic Curve Cryptography that we're aware of, either only "named curves" are supported, or, if explicit curve parameters are supported, they specify an X9.62 encoding of binary (GF(2^m)) curves that can't represent problematic input values. Thus the likelihood of existence of a vulnerable application is low. In particular, the X9.62 encoding is used for ECC keys in X.509 certificates, so problematic inputs cannot occur in the context of processing X.509 certificates. Any problematic use-cases would have to be using an "exotic" curve encoding. The affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(), and various supporting BN_GF2m_*() functions. Applications working with "exotic" explicit binary (GF(2^m)) curve parameters, that make it possible to represent invalid field polynomials with a zero constant term, via the above or similar APIs, may terminate abruptly as a result of reading or writing outside of array bounds. Remote code execution cannot easily be ruled out. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.


Затронутые продукты
Container bci/bci-base-fips:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-base-fips:latest:libopenssl3-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl3-3.5.0-150700.5.45.2

Ссылки

Описание

Issue summary: PBMAC1 parameters in PKCS#12 files are missing validation which can trigger a stack-based buffer overflow, invalid pointer or NULL pointer dereference during MAC verification. Impact summary: The stack buffer overflow or NULL pointer dereference may cause a crash leading to Denial of Service for an application that parses untrusted PKCS#12 files. The buffer overflow may also potentially enable code execution depending on platform mitigations. When verifying a PKCS#12 file that uses PBMAC1 for the MAC, the PBKDF2 salt and keylength parameters from the file are used without validation. If the value of keylength exceeds the size of the fixed stack buffer used for the derived key (64 bytes), the key derivation will overflow the buffer. The overflow length is attacker-controlled. Also, if the salt parameter is not an OCTET STRING type this can lead to invalid or NULL pointer dereference. Exploiting this issue requires a user or application to process a maliciously crafted PKCS#12 file. It is uncommon to accept untrusted PKCS#12 files in applications as they are usually used to store private keys which are trusted by definition. For this reason the issue was assessed as Moderate severity. The FIPS modules in 3.6, 3.5 and 3.4 are not affected by this issue, as PKCS#12 processing is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5 and 3.4 are vulnerable to this issue. OpenSSL 3.3, 3.0, 1.1.1 and 1.0.2 are not affected by this issue as they do not support PBMAC1 in PKCS#12.


Затронутые продукты
Container bci/bci-base-fips:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-base-fips:latest:libopenssl3-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl3-3.5.0-150700.5.45.2

Ссылки

Описание

Issue summary: If an application using the SSL_CIPHER_find() function in a QUIC protocol client or server receives an unknown cipher suite from the peer, a NULL dereference occurs. Impact summary: A NULL pointer dereference leads to abnormal termination of the running process causing Denial of Service. Some applications call SSL_CIPHER_find() from the client_hello_cb callback on the cipher ID received from the peer. If this is done with an SSL object implementing the QUIC protocol, NULL pointer dereference will happen if the examined cipher ID is unknown or unsupported. As it is not very common to call this function in applications using the QUIC protocol and the worst outcome is Denial of Service, the issue was assessed as Low severity. The vulnerable code was introduced in the 3.2 version with the addition of the QUIC protocol support. The FIPS modules in 3.6, 3.5, 3.4 and 3.3 are not affected by this issue, as the QUIC implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4 and 3.3 are vulnerable to this issue. OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue.


Затронутые продукты
Container bci/bci-base-fips:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-base-fips:latest:libopenssl3-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl3-3.5.0-150700.5.45.2

Ссылки

Описание

Issue summary: The 'openssl dgst' command-line tool silently truncates input data to 16MB when using one-shot signing algorithms and reports success instead of an error. Impact summary: A user signing or verifying files larger than 16MB with one-shot algorithms (such as Ed25519, Ed448, or ML-DSA) may believe the entire file is authenticated while trailing data beyond 16MB remains unauthenticated. When the 'openssl dgst' command is used with algorithms that only support one-shot signing (Ed25519, Ed448, ML-DSA-44, ML-DSA-65, ML-DSA-87), the input is buffered with a 16MB limit. If the input exceeds this limit, the tool silently truncates to the first 16MB and continues without signaling an error, contrary to what the documentation states. This creates an integrity gap where trailing bytes can be modified without detection if both signing and verification are performed using the same affected codepath. The issue affects only the command-line tool behavior. Verifiers that process the full message using library APIs will reject the signature, so the risk primarily affects workflows that both sign and verify with the affected 'openssl dgst' command. Streaming digest algorithms for 'openssl dgst' and library users are unaffected. The FIPS modules in 3.5 and 3.6 are not affected by this issue, as the command-line tools are outside the OpenSSL FIPS module boundary. OpenSSL 3.5 and 3.6 are vulnerable to this issue. OpenSSL 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are not affected by this issue.


Затронутые продукты
Container bci/bci-base-fips:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-base-fips:latest:libopenssl3-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl3-3.5.0-150700.5.45.2

Ссылки

Описание

OpenSSL 3.0.0 through 3.3.2 on the PowerPC architecture is vulnerable to a Minerva attack, exploitable by measuring the time of signing of random messages using the EVP_DigestSign API, and then using the private key to extract the K value (nonce) from the signatures. Next, based on the bit size of the extracted nonce, one can compare the signing time of full-sized nonces to signatures that used smaller nonces, via statistical tests. There is a side-channel in the P-364 curve that allows private key extraction (also, there is a dependency between the bit size of K and the size of the side channel). NOTE: This CVE is disputed because the OpenSSL security policy explicitly notes that any side channels which require same physical system to be detected are outside of the threat model for the software. The timing signal is so small that it is infeasible to be detected without having the attacking process running on the same physical system.


Затронутые продукты
Container bci/bci-base-fips:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-base-fips:latest:libopenssl3-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl3-3.5.0-150700.5.45.2

Ссылки

Описание

Issue summary: Use of -addreject option with the openssl x509 application adds a trusted use instead of a rejected use for a certificate. Impact summary: If a user intends to make a trusted certificate rejected for a particular use it will be instead marked as trusted for that use. A copy & paste error during minor refactoring of the code introduced this issue in the OpenSSL 3.5 version. If, for example, a trusted CA certificate should be trusted only for the purpose of authenticating TLS servers but not for CMS signature verification and the CMS signature verification is intended to be marked as rejected with the -addreject option, the resulting CA certificate will be trusted for CMS signature verification purpose instead. Only users which use the trusted certificate format who use the openssl x509 command line application to add rejected uses are affected by this issue. The issues affecting only the command line application are considered to be Low severity. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL 3.4, 3.3, 3.2, 3.1, 3.0, 1.1.1 and 1.0.2 are also not affected by this issue.


Затронутые продукты
Container bci/bci-base-fips:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-base-fips:latest:libopenssl3-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl3-3.5.0-150700.5.45.2

Ссылки

Описание

Issue summary: A TLS 1.3 connection using certificate compression can be forced to allocate a large buffer before decompression without checking against the configured certificate size limit. Impact summary: An attacker can cause per-connection memory allocations of up to approximately 22 MiB and extra CPU work, potentially leading to service degradation or resource exhaustion (Denial of Service). In affected configurations, the peer-supplied uncompressed certificate length from a CompressedCertificate message is used to grow a heap buffer prior to decompression. This length is not bounded by the max_cert_list setting, which otherwise constrains certificate message sizes. An attacker can exploit this to cause large per-connection allocations followed by handshake failure. No memory corruption or information disclosure occurs. This issue only affects builds where TLS 1.3 certificate compression is compiled in (i.e., not OPENSSL_NO_COMP_ALG) and at least one compression algorithm (brotli, zlib, or zstd) is available, and where the compression extension is negotiated. Both clients receiving a server CompressedCertificate and servers in mutual TLS scenarios receiving a client CompressedCertificate are affected. Servers that do not request client certificates are not vulnerable to client-initiated attacks. Users can mitigate this issue by setting SSL_OP_NO_RX_CERTIFICATE_COMPRESSION to disable receiving compressed certificates. The FIPS modules in 3.6, 3.5, 3.4 and 3.3 are not affected by this issue, as the TLS implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4 and 3.3 are vulnerable to this issue. OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue.


Затронутые продукты
Container bci/bci-base-fips:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-base-fips:latest:libopenssl3-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl3-3.5.0-150700.5.45.2

Ссылки

Описание

Issue summary: A timing side-channel which could potentially allow remote recovery of the private key exists in the SM2 algorithm implementation on 64 bit ARM platforms. Impact summary: A timing side-channel in SM2 signature computations on 64 bit ARM platforms could allow recovering the private key by an attacker.. While remote key recovery over a network was not attempted by the reporter, timing measurements revealed a timing signal which may allow such an attack. OpenSSL does not directly support certificates with SM2 keys in TLS, and so this CVE is not relevant in most TLS contexts. However, given that it is possible to add support for such certificates via a custom provider, coupled with the fact that in such a custom provider context the private key may be recoverable via remote timing measurements, we consider this to be a Moderate severity issue. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as SM2 is not an approved algorithm.


Затронутые продукты
Container bci/bci-base-fips:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-base-fips:latest:libopenssl3-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl3-3.5.0-150700.5.45.2

Ссылки

Описание

Issue summary: An application using the OpenSSL HTTP client API functions may trigger an out-of-bounds read if the 'no_proxy' environment variable is set and the host portion of the authority component of the HTTP URL is an IPv6 address. Impact summary: An out-of-bounds read can trigger a crash which leads to Denial of Service for an application. The OpenSSL HTTP client API functions can be used directly by applications but they are also used by the OCSP client functions and CMP (Certificate Management Protocol) client implementation in OpenSSL. However the URLs used by these implementations are unlikely to be controlled by an attacker. In this vulnerable code the out of bounds read can only trigger a crash. Furthermore the vulnerability requires an attacker-controlled URL to be passed from an application to the OpenSSL function and the user has to have a 'no_proxy' environment variable set. For the aforementioned reasons the issue was assessed as Low severity. The vulnerable code was introduced in the following patch releases: 3.0.16, 3.1.8, 3.2.4, 3.3.3, 3.4.0 and 3.5.0. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the HTTP client implementation is outside the OpenSSL FIPS module boundary.


Затронутые продукты
Container bci/bci-base-fips:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-base-fips:latest:libopenssl3-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl3-3.5.0-150700.5.45.2

Ссылки

Описание

Issue summary: An OpenSSL TLS 1.3 server may fail to negotiate the expected preferred key exchange group when its key exchange group configuration includes the default by using the 'DEFAULT' keyword. Impact summary: A less preferred key exchange may be used even when a more preferred group is supported by both client and server, if the group was not included among the client's initial predicated keyshares. This will sometimes be the case with the new hybrid post-quantum groups, if the client chooses to defer their use until specifically requested by the server. If an OpenSSL TLS 1.3 server's configuration uses the 'DEFAULT' keyword to interpolate the built-in default group list into its own configuration, perhaps adding or removing specific elements, then an implementation defect causes the 'DEFAULT' list to lose its 'tuple' structure, and all server-supported groups were treated as a single sufficiently secure 'tuple', with the server not sending a Hello Retry Request (HRR) even when a group in a more preferred tuple was mutually supported. As a result, the client and server might fail to negotiate a mutually supported post-quantum key agreement group, such as 'X25519MLKEM768', if the client's configuration results in only 'classical' groups (such as 'X25519' being the only ones in the client's initial keyshare prediction). OpenSSL 3.5 and later support a new syntax for selecting the most preferred TLS 1.3 key agreement group on TLS servers. The old syntax had a single 'flat' list of groups, and treated all the supported groups as sufficiently secure. If any of the keyshares predicted by the client were supported by the server the most preferred among these was selected, even if other groups supported by the client, but not included in the list of predicted keyshares would have been more preferred, if included. The new syntax partitions the groups into distinct 'tuples' of roughly equivalent security. Within each tuple the most preferred group included among the client's predicted keyshares is chosen, but if the client supports a group from a more preferred tuple, but did not predict any corresponding keyshares, the server will ask the client to retry the ClientHello (by issuing a Hello Retry Request or HRR) with the most preferred mutually supported group. The above works as expected when the server's configuration uses the built-in default group list, or explicitly defines its own list by directly defining the various desired groups and group 'tuples'. No OpenSSL FIPS modules are affected by this issue, the code in question lies outside the FIPS boundary. OpenSSL 3.6 and 3.5 are vulnerable to this issue. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.2 once it is released. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.6 once it is released. OpenSSL 3.4, 3.3, 3.0, 1.0.2 and 1.1.1 are not affected by this issue.


Затронутые продукты
Container bci/bci-base-fips:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-base-fips:latest:libopenssl3-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl3-3.5.0-150700.5.45.2

Ссылки

Описание

Issue summary: During processing of a crafted CMS EnvelopedData message with KeyTransportRecipientInfo a NULL pointer dereference can happen. Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resulting in Denial of Service. When a CMS EnvelopedData message that uses KeyTransportRecipientInfo with RSA-OAEP encryption is processed, the optional parameters field of RSA-OAEP SourceFunc algorithm identifier is examined without checking for its presence. This results in a NULL pointer dereference if the field is missing. Applications and services that call CMS_decrypt() on untrusted input (e.g., S/MIME processing or CMS-based protocols) are vulnerable. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.


Затронутые продукты
Container bci/bci-base-fips:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-base-fips:latest:libopenssl3-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl3-3.5.0-150700.5.45.2

Ссылки

Описание

Issue Summary: Cryptographic Message Services (CMS) processing fails to perform sufficient input validation on the cipher and tag length fields of AuthEnvelopedData containers, leading to various potential compromises. Impact Summary: Attackers making use of these vulnerabilities may achieve key-equivalent functionality for a given CMS recipient and/or bypass integrity validation for a given message. In one use case, an attacker may send a CMS message containing AuthEnvelopedData with the cipher specified as a non-AEAD cipher. OpenSSL erroneously allows this selection, and attempts to decrypt and validate the message. An on-path attacker who captures one legitimate AES-GCM AuthEnvelopedData addressed to the victim can re-emit it with the recipientInfos set left byte-for-byte intact, so the victim's private key still unwraps the genuine CEK (the content-encryption key), but with the inner OID rewritten to AES-256-OFB (Output Feedback Mode, an unauthenticated keystream mode) and with an attacker-chosen IV and ciphertext. The victim initializes AES-256-OFB under the real CEK, never consults the MAC field, and CMS_decrypt() returns success. If the application under attack responds to the attacker with any indicator showing success or failure of the decryption effort, it is possible for the attacker to use this as an oracle to obtain key equivalent functionality for the CEK used for the chosen recipient of the message. In another use case, an attacker can reduce the tag length of the chosen AEAD cipher for a given AuthEnvelopedData container to be a single byte long, allowing an attacker to brute force CMS decryption, producing an integrity bypass for applications that trust CMS_decrypt() to reject modified content. The FIPS modules are not affected by this issue.


Затронутые продукты
Container bci/bci-base-fips:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-base-fips:latest:libopenssl3-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl3-3.5.0-150700.5.45.2

Ссылки

Описание

Issue summary: Receiving a QUIC initial packet with an invalid token may trigger a NULL pointer dereference in the OpenSSL QUIC server with address validation disabled. Impact summary: NULL pointer dereference typically causes abnormal termination of the affected QUIC server process and a Denial of Service. If the address validation is disabled in the OpenSSL QUIC server implementation, an attacker can crash the server by sending an initial packet with an invalid or expired token. By default, the client address validation is enabled in the OpenSSL QUIC server implementation, which makes the default configuration not vulnerable to this issue. However if the SSL_LISTENER_FLAG_NO_VALIDATE is used with the SSL_new_listener() call, the address validation is disabled making the vulnerable code reachable. The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.


Затронутые продукты
Container bci/bci-base-fips:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-base-fips:latest:libopenssl3-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl-3-fips-provider-3.5.0-150700.5.45.2
Container bci/bci-init:latest:libopenssl3-3.5.0-150700.5.45.2

Ссылки
Уязвимость SUSE-SU-2026:3835-1