aboutsummaryrefslogtreecommitdiff
path: root/crypto/openssl/CHANGES.md
diff options
context:
space:
mode:
Diffstat (limited to 'crypto/openssl/CHANGES.md')
-rw-r--r--crypto/openssl/CHANGES.md126
1 files changed, 126 insertions, 0 deletions
diff --git a/crypto/openssl/CHANGES.md b/crypto/openssl/CHANGES.md
index 2978ebfa2d10..b991285aedb2 100644
--- a/crypto/openssl/CHANGES.md
+++ b/crypto/openssl/CHANGES.md
@@ -28,6 +28,129 @@ OpenSSL Releases
OpenSSL 3.5
-----------
+### Changes between 3.5.3 and 3.5.4 [30 Sep 2025]
+
+ * Fix Out-of-bounds read & write in RFC 3211 KEK Unwrap
+
+ Issue summary: An application trying to decrypt CMS messages encrypted using
+ password based encryption can trigger an out-of-bounds read and write.
+
+ Impact summary: This out-of-bounds read may trigger a crash which leads to
+ Denial of Service for an application. The out-of-bounds write can cause
+ a memory corruption which can have various consequences including
+ a Denial of Service or Execution of attacker-supplied code.
+
+ The issue was reported by Stanislav Fort (Aisle Research).
+
+ ([CVE-2025-9230])
+
+ *Viktor Dukhovni*
+
+ * Fix Timing side-channel in SM2 algorithm on 64 bit ARM
+
+ 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.
+
+ The issue was reported by Stanislav Fort (Aisle Research).
+
+ ([CVE-2025-9231])
+
+ *Stanislav Fort and Tomáš Mráz*
+
+ * Fix Out-of-bounds read in HTTP client no_proxy handling
+
+ 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 issue was reported by Stanislav Fort (Aisle Research).
+
+ ([CVE-2025-9232])
+
+ *Stanislav Fort*
+
+ * The FIPS provider no longer performs a PCT on key import for ECX keys
+ (that was introduced in 3.5.2), following the latest update
+ on that requirement in FIPS 140-3 IG 10.3.A additional comment 1.
+
+ *Eugene Syromiatnikov*
+
+ * Fixed the length of the ASN.1 sequence for the SM3 digests of RSA-encrypted
+ signatures.
+
+ *Xiao Lou Dong Feng*
+
+ * Reverted the synthesised `OPENSSL_VERSION_NUMBER` change for the release
+ builds, as it broke some exiting applications that relied on the previous
+ 3.x semantics, as documented in `OpenSSL_version(3)`.
+
+ *Richard Levitte*
+
+### Changes between 3.5.2 and 3.5.3 [16 Sep 2025]
+
+ * Avoided a potential race condition introduced in 3.5.1, where
+ `OSSL_STORE_CTX` kept open during lookup while potentially being used
+ by multiple threads simultaneously, that could lead to potential crashes
+ when multiple concurrent TLS connections are served.
+
+ *Matt Caswell*
+
+ * The FIPS provider no longer performs a PCT on key import for RSA, DH,
+ and EC keys (that was introduced in 3.5.2), following the latest update
+ on that requirement in FIPS 140-3 IG 10.3.A additional comment 1.
+
+ *Dr Paul Dale*
+
+ * Secure memory allocation calls are no longer used for HMAC keys.
+
+ *Dr Paul Dale*
+
+ * `openssl req` no longer generates certificates with an empty extension list
+ when SKID/AKID are set to `none` during generation.
+
+ *David Benjamin*
+
+ * The man page date is now derived from the release date provided
+ in `VERSION.dat` and not the current date for the released builds.
+
+ *Enji Cooper*
+
+ * Hardened the provider implementation of the RSA public key "encrypt"
+ operation to add a missing check that the caller-indicated output buffer
+ size is at least as large as the byte count of the RSA modulus. The issue
+ was reported by Arash Ale Ebrahim from SYSPWN.
+
+ This operation is typically invoked via `EVP_PKEY_encrypt(3)`. Callers that
+ in fact provide a sufficiently large buffer, but fail to correctly indicate
+ its size may now encounter unexpected errors. In applications that attempt
+ RSA public encryption into a buffer that is too small, an out-of-bounds
+ write is now avoided and an error is reported instead.
+
+ *Viktor Dukhovni*
+
+ * Added FIPS 140-3 PCT on DH key generation.
+
+ *Nikola Pajkovsky*
+
+ * Fixed the synthesised `OPENSSL_VERSION_NUMBER`.
+
+ *Richard Levitte*
+
+### Changes between 3.5.1 and 3.5.2 [5 Aug 2025]
+
+ * The FIPS provider now performs a PCT on key import for RSA, EC and ECX.
+ This is mandated by FIPS 140-3 IG 10.3.A additional comment 1.
+
+ *Dr Paul Dale*
+
### Changes between 3.5.0 and 3.5.1 [1 Jul 2025]
* Fix x509 application adds trusted use instead of rejected use.
@@ -21227,6 +21350,9 @@ ndif
<!-- Links -->
+[CVE-2025-9232]: https://www.openssl.org/news/vulnerabilities.html#CVE-2025-9232
+[CVE-2025-9231]: https://www.openssl.org/news/vulnerabilities.html#CVE-2025-9231
+[CVE-2025-9230]: https://www.openssl.org/news/vulnerabilities.html#CVE-2025-9230
[CVE-2025-4575]: https://www.openssl.org/news/vulnerabilities.html#CVE-2025-4575
[CVE-2024-13176]: https://www.openssl.org/news/vulnerabilities.html#CVE-2024-13176
[CVE-2024-9143]: https://www.openssl.org/news/vulnerabilities.html#CVE-2024-9143