|
| 1 | +# wolfSSL Release 5.6.6 (Dec 19, 2023) |
| 2 | + |
| 3 | +Release 5.6.6 has been developed according to wolfSSL's development and QA |
| 4 | +process (see link below) and successfully passed the quality criteria. |
| 5 | +https://www.wolfssl.com/about/wolfssl-software-development-process-quality-assurance |
| 6 | + |
| 7 | +NOTE: * --enable-heapmath is being deprecated and will be removed by 2024 |
| 8 | + |
| 9 | +REMINDER: When working with AES Block Cipher algorithms, `wc_AesInit()` should |
| 10 | +always be called first to initialize the `Aes` structure, before calling other |
| 11 | +Aes API functions. Recently we found several places in our documentation, |
| 12 | +comments, and codebase where this pattern was not observed. We have since |
| 13 | +fixed this omission in several PRs for this release. |
| 14 | + |
| 15 | +## Vulnerabilities |
| 16 | + |
| 17 | +* [Medium] CVE-2023-6935: After review of the previous RSA timing fix in wolfSSL 5.6.4, additional changes were found to be required. A complete resistant change is delivered in this release. This fix is for the Marvin attack, leading to being able to decrypt a saved TLS connection and potentially forge a signature after probing with a very large number of trial connections. This issue is around RSA decryption and affects the optional static RSA cipher suites on the server side, which are considered weak, not recommended to be used and are off by default in wolfSSL (even with `--enable-all`). Static RSA cipher suites were also removed from the TLS 1.3 protocol and are only present in TLS 1.2 and lower. All padding versions of RSA decrypt are affected since the code under review is outside of the padding processing. Information about the private keys is NOT compromised in affected code. It is recommended to disable static RSA cipher suites and update the version of wolfSSL used if using RSA private decryption alone outside of TLS. Thanks to Hubert Kario for the report. The fix for this issue is located in the following GitHub Pull Request: https://github.com/wolfSSL/wolfssl/pull/6955. |
| 18 | + |
| 19 | +* [Low] CVE-2023-6936: A potential heap overflow read is possible in servers connecting over TLS 1.3 when the optional `WOLFSSL_CALLBACKS` has been defined. The out of bounds read can occur when a server receives a malicious malformed ClientHello. Users should either discontinue use of `WOLFSSL_CALLBACKS` on the server side or update versions of wolfSSL to 5.6.6. Thanks to the tlspuffin fuzzer team for the report which was designed and developed by; Lucca Hirschi (Inria, LORIA), Steve Kremer (Inria, LORIA), and Max Ammann (Trail of Bits). The fix for this issue is located in the following GitHub Pull Request: https://github.com/wolfSSL/wolfssl/pull/6949. |
| 20 | + |
| 21 | +* [Low] A side channel vulnerability with AES T-Tables is possible in a very controlled environment where precision sub-cache-line inspection can happen, such as inside an Intel SGX enclave. This can lead to recovery of the AES key. To prevent this type of attack, wolfSSL added an AES bitsliced implementation which can be enabled with the “`--enable-aes-bitsliced`” configure option. Thanks to Florian Sieck, Zhiyuan Zhang, Sebastian Berndt, Chitchanok Chuengsatiansup, Thomas Eisenbarth, and Yuval Yarom for the report (Universities of Lübeck, Melbourne, Adelaide and Bochum). The fix for this issue is located in the following GitHub Pull Request: https://github.com/wolfSSL/wolfssl/pull/6854. |
| 22 | + |
| 23 | +* [Low] CVE-2023-6937: wolfSSL prior to 5.6.6 did not check that messages in a single (D)TLS record do not span key boundaries. As a result, it was possible to combine (D)TLS messages using different keys into one (D)TLS record. The most extreme edge case is that, in (D)TLS 1.3, it was possible that an unencrypted (D)TLS 1.3 record from the server containing first a ServerHello message and then the rest of the first server flight would be accepted by a wolfSSL client. In (D)TLS 1.3 the handshake is encrypted after the ServerHello but a wolfSSL client would accept an unencrypted flight from the server. This does not compromise key negotiation and authentication so it is assigned a low severity rating. Thanks to Johannes Wilson for the report (Sectra Communications and Linköping University). The fix for this issue is located in the following GitHub Pull Request: https://github.com/wolfSSL/wolfssl/pull/7029. |
| 24 | + |
| 25 | +## New Feature Additions |
| 26 | + |
| 27 | +* Build option for disabling CRL date checks (`WOLFSSL_NO_CRL_DATE_CHECK`) (PR 6927) |
| 28 | +* Support for STM32WL55 and improvements to PKA ECC support (PR 6937) |
| 29 | +* Add option to skip cookie exchange on DTLS 1.3 session resumption (PR 6929) |
| 30 | +* Add implementation of SRTP KDF and SRTCP KDF (`--enable-srtp-kdf`) (PR 6888) |
| 31 | +* Add `wolfSSL_EXTENDED_KEY_USAGE_free()` (PR 6916) |
| 32 | +* Add AES bitsliced implementation that is cache attack safe (`--enable-aes-bitsliced`) (PR 6854) |
| 33 | +* Add memcached support and automated testing (PR 6430, 7022) |
| 34 | +* Add Hardware Encryption Acceleration for ESP32-C3, ESP32-C6, and ESP32-S2 (PR 6990) |
| 35 | +* Add (D)TLS 1.3 support for 0.5-RTT data (PR 7010) |
| 36 | + |
| 37 | +## Enhancements and Optimizations |
| 38 | + |
| 39 | +* Better built in testing of “`--sys-ca-certs`” configure option (PR 6910) |
| 40 | +* Updated CMakeLists.txt for Espressif wolfSSL component usage (PR 6877) |
| 41 | +* Disable TLS 1.1 by default (unless SSL 3.0 or TLS 1.0 is enabled) (PR 6946) |
| 42 | +* Add “`--enable-quic`” to “`--enable-all`” configure option (PR 6957) |
| 43 | +* Add support to SP C implementation for RSA exponent up to 64-bits (PR 6959) |
| 44 | +* Add result of “`HAVE___UINT128_T`” to options.h for CMake builds (PR 6965) |
| 45 | +* Add optimized assembly for AES-GCM on ARM64 using hardware crypto instructions (PR 6967) |
| 46 | +* Add built-in cipher suite tests for DTLS 1.3 PQC (PR 6952) |
| 47 | +* Add wolfCrypt test and unit test to ctest (PR 6977) |
| 48 | +* Move OpenSSL compatibility crypto APIs into `ssl_crypto.c` file (PR 6935) |
| 49 | +* Validate time generated from XGMTIME() (PR 6958) |
| 50 | +* Allow wolfCrypt benchmark to run with microsecond accuracy (PR 6868) |
| 51 | +* Add GitHub Actions testing with nginx 1.24.0 (PR 6982) |
| 52 | +* Allow encoding of CA:FALSE BasicConstraint during cert generation (PR 6953) |
| 53 | +* Add CMake option to enable DTLS-SRTP (PR 6991) |
| 54 | +* Add CMake options for enabling QUIC and cURL (PR 7049) |
| 55 | +* Improve RSA blinding to make code more constant time (PR 6955) |
| 56 | +* Refactor AES-NI implementation macros to allow dynamic fallback to C (PR 6981) |
| 57 | +* Default to native Windows threading API on MinGW (PR 7015) |
| 58 | +* Return better error codes from OCSP response check (PR 7028) |
| 59 | +* Updated Espressif ESP32 TLS client and server examples (PR 6844) |
| 60 | +* Add/clean up support for ESP-IDF v5.1 for a variety of ESP32 chips (PR 7035, 7037) |
| 61 | +* Add API to choose dynamic certs based on client ciphers/sigalgs (PR 6963) |
| 62 | +* Improve Arduino IDE 1.5 project file to match recursive style (PR 7007) |
| 63 | +* Simplify and improve apple-universal build script (PR 7025) |
| 64 | + |
| 65 | +## Fixes |
| 66 | + |
| 67 | +* Fix for async edge case with Intel QuickAssist/Cavium Nitrox (PR 6931) |
| 68 | +* Fix for building PKCS#7 with RSA disabled (PR 6902) |
| 69 | +* Fix for advancing output pointer in `wolfSSL_i2d_X509()` (PR 6891) |
| 70 | +* Fix for `EVP_EncodeBlock()` appending a newline (PR 6900) |
| 71 | +* Fix for `wolfSSL_RSA_verify_PKCS1_PSS()` with `RSA_PSS_SALTLEN_AUTO` (PR 6938) |
| 72 | +* Fixes for CODESonar reports around `isalpha()` and `isalnum()` calls (PR 6810) |
| 73 | +* Fix for SP ARM64 integer math to avoid compiler optimization issues (PR 6942) |
| 74 | +* Fix for SP Thumb2 inline assembly to add IAR build support (PR 6943, 6971) |
| 75 | +* Fix for SP Thumb2 to make functions not inlined (PR 6993) |
| 76 | +* Fix for SP Cortex-M assembly large build with IAR (PR 6954) |
| 77 | +* Fix for SP ARM64 assembly montgomery reduction by 4 (PR 6947) |
| 78 | +* Fix for SP ARM64 P-256 for not inlining functions for iOS compatibility (PR 6979) |
| 79 | +* Fix for `WOLFSSL_CALLBACKS` and potential memory error (PR 6949) |
| 80 | +* Fixes for wolfSSL’s Zephyr OS port (PR 6930) |
| 81 | +* Fix for build errors when building for NXP mmCAU (`FREESCALE_MMCAU`) (PR 6970) |
| 82 | +* Fix for TLS 1.3 `SendBuffered()` return code in non-blocking mode (PR 7001) |
| 83 | +* Fix for TLS `Hmac_UpdateFinal()` when padding byte is invalid (PR 6998) |
| 84 | +* Fix for ARMv8 AES-GCM streaming to check size of IV before storing (PR 6996) |
| 85 | +* Add missing calls to `wc_AesInit()` before `wc_AesSetKey()` (PR 7011) |
| 86 | +* Fix build errors with DTLS 1.3 enabled but TLS 1.2 disabled (PR 6976) |
| 87 | +* Fixes for building wolfSSL in Visual Studio (PR 7040) |
| 88 | + |
1 | 89 | # wolfSSL Release 5.6.4 (Oct 30, 2023) |
2 | 90 |
|
3 | 91 | Release 5.6.4 has been developed according to wolfSSL's development and QA process (see link below) and successfully passed the quality criteria. |
4 | 92 | https://www.wolfssl.com/about/wolfssl-software-development-process-quality-assurance |
5 | 93 |
|
6 | | - |
7 | 94 | NOTE: * --enable-heapmath is being deprecated and will be removed by 2024 |
8 | 95 | * Old CyaSSL/CtaoCrypt shim layer was removed in this release (5.6.4) |
9 | 96 |
|
10 | | - |
11 | 97 | ## Vulnerabilities |
12 | 98 |
|
13 | 99 | * [Medium] A fix was added, but still under review for completeness, for a Bleichenbacher style attack, leading to being able to decrypt a saved TLS connection and potentially forge a signature after probing with a large number of trial connections. This issue is around RSA decryption and affects static RSA cipher suites on the server side, which are not recommended to be used and are off by default. Static RSA cipher suites were also removed from the TLS 1.3 protocol and only present in TLS 1.2 and lower. All padding versions of RSA decrypt are affected since the code under review is outside of the padding processing. Information about the private keys is NOT compromised in affected code. It's recommended to disable static RSA cipher suites and update the version of wolfSSL used if using RSA private decryption alone outside of TLS. The fix is located in this pull request (https://github.com/wolfSSL/wolfssl/pull/6896) |
@@ -70,7 +156,6 @@ Release 5.6.3 of wolfSSL embedded TLS has 4 bug fixes: |
70 | 156 | * Improvements to Encrypted Memory support (WC_PROTECT_ENCRYPTED_MEM) implementations for modular exponentiation in SP math-all (sp_int.c) and TFM (tfm.c). |
71 | 157 | * Improvements to SendAlert for getting output buffer. |
72 | 158 |
|
73 | | - |
74 | 159 | # wolfSSL Release 5.6.2 (Jun 09, 2023) |
75 | 160 |
|
76 | 161 | Release 5.6.2 has been developed according to wolfSSL's development and QA process (see link below) and successfully passed the quality criteria. |
|
0 commit comments