{"id":144089,"date":"2025-10-03T17:12:04","date_gmt":"2025-10-03T15:12:04","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-openssl-3-6-0-s-podderzhkoj-evp_skey-i-ustraneniem-perepolneniya-bufera"},"modified":"2025-10-03T17:12:04","modified_gmt":"2025-10-03T15:12:04","slug":"vypusk-openssl-3-6-0-s-podderzhkoj-evp_skey-i-ustraneniem-perepolneniya-bufera","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-openssl-3-6-0-s-podderzhkoj-evp_skey-i-ustraneniem-perepolneniya-bufera","title":{"rendered":"Release of OpenSSL 3.6.0 with EVP_SKEY support and buffer overflow fixes","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The release of OpenSSL 3.6.0 has occurred, offering the implementation of SSL\/TLS protocols and various encryption algorithms. OpenSSL 3.6 is classified as a standard-support release, with updates being issued for 13 months. Support for previous branches OpenSSL 3.5 LTS, 3.4, 3.3, 3.2, and 3.0 LTS will last until April 2030, October 2026, April 2026, November 2025, and September 2026, respectively. The project's code is distributed under the Apache 2.0 license. <\/p>\n
Key innovations: <\/p>\n
\n
Support for the EVP_SKEY structure (Symmetric KEY) has been added to represent symmetric keys as opaque objects. Unlike raw keys represented as byte arrays, the EVP_SKEY structure abstracts the key and contains additional metadata. Usage of EVP_SKEY is permitted in encryption functions, key exchange, and key derivation functions (KDF). Functions EVP_KDF_CTX_set_SKEY(), EVP_KDF_derive_SKEY(), and EVP_PKEY_derive_SKEY() have been added for working with EVP_SKEY keys.\n
Support for digital signature verification based on the LMS (Leighton-Micali Signatures) scheme has been added, utilizing hash functions and tree hashing in the form of a Merkle Tree (each branch verifies all underlying branches and nodes). LMS digital signatures are resistant to key search on quantum computers and are designed to ensure the integrity of firmware and applications.\n
Support for NIST security categories has been added for PKEY object parameters (both public and private keys). The security category is set through the \"security-category\" configuration. The function EVP_PKEY_get_security_category() has been added to check the security level. The security level reflects resistance to attacks by quantum computers and can take integer values from 0 to 5:\n
\n
0 \u2014 implementation that is not resistant to attacks by quantum computers;\n
1\/3\/5 \u2014 implementation does not rule out the search for a key by a quantum computer in a block cipher with a 128\/192\/256-bit key;\n
2\/4 \u2014 implementation does not rule out the search for collisions in a 256\/384-bit hash by a quantum computer). <\/ul>\n
The command \"openssl configutl\" has been added for processing the configuration file. The utility allows the creation of a consolidated file with all settings based on a multi-file configuration with include directives.\n
The FIPS cryptoprovider now supports deterministic generation of ECDSA digital signatures (the same signature is generated for the same inputs), in accordance with the requirements of the FIPS 186-5 standard.\n
The requirements for the build environment have been raised. It is no longer sufficient to have ANSI-C compliant tools for building OpenSSL; a compiler compatible with the C-99 standard is now required.\n
Functions related to the EVP_PKEY_ASN1_METHOD structure have been deprecated.\n
Support for the VxWorks platform has been discontinued. <\/ul>\n
Fixed vulnerabilities: <\/p>\n
\n
CVE-2025-9230 \u2014 a vulnerability in the code for decrypting CMS messages encrypted using a password (PWRI). This vulnerability can lead to writing and reading data outside the allocated buffer, potentially causing a crash or memory corruption in applications using OpenSSL to process CMS messages. Exploitation of this vulnerability might allow for arbitrary code execution, but the risk is mitigated by the fact that CMS message encryption using a password is very rarely used in practice. In addition to OpenSSL version 3.6.0, the vulnerability has been fixed in releases 3.5.4, 3.4.3, 3.3.5, 3.2.6, and 3.0.18. The issue is also resolved in library updates LibreSSL 4.0.1 and 4.1.1, maintained by the OpenBSD project.\n
CVE-2025-9231 \u2014 the implementation of the SM2 algorithm is vulnerable to side-channel attacks, allowing the recreation of the private key on systems with 64-bit ARM CPUs by analyzing execution time variations of individual computations. The attack can potentially be carried out remotely. The risk of this attack is lowered since OpenSSL does not directly support the use of certificates with SM2 keys in TLS.\n
CVE-2025-9232 \u2014 a vulnerability in the implementation of the built-in HTTP client that allows reading data from out-of-bounds memory when handling specially formatted URLs in HTTP Client functions. The issue occurs only when the environment variable \"no_proxy\" is set and may lead to application crashes. <\/ul>\n