OpenSSL 3.0.0 < 3.0.10 Multiple Vulnerabilities on Win server 2016 and 2019

Question

Plugin Output: Reported version : 3.0.3.0 Fixed version : 3.0.10

Will Microsoft issue a fix for the below mentioned vulnerability ? The version of OpenSSL installed on the remote host is prior to 3.0.10. It is, therefore, affected by multiple vulnerabilities as referenced in the 3.0.10 advisory.

• Issue summary: Checking excessively long DH keys or parameters may be very slow. Impact summary: Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key or DH 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 function DH_check() performs various checks on DH parameters. One of those checks confirms that the modulus ('p' parameter) is not too large. Trying to use a very large modulus is slow and OpenSSL will not normally use a modulus which is over 10,000 bits in length. However the DH_check() function checks numerous aspects of the key or parameters that have been supplied. Some of those checks use the supplied modulus value even if it has already been found to be too large. An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulernable to a Denial of Service attack. The function DH_check() is itself called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_ex() and EVP_PKEY_param_check(). Also vulnerable are the OpenSSL dhparam 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 not affected by this issue. (CVE-2023-3446)
• Issue summary: The AES-SIV cipher implementation contains a bug that causes it to ignore empty associated data entries which are unauthenticated as a consequence. Impact summary: Applications that use the AES-SIV algorithm and want to authenticate empty data entries as associated data can be mislead by removing adding or reordering such empty entries as these are ignored by the OpenSSL implementation. We are currently unaware of any such applications. The AES-SIV algorithm allows for authentication of multiple associated data entries along with the encryption. To authenticate empty data the application has to call EVP_EncryptUpdate() (or EVP_CipherUpdate()) with NULL pointer as the output buffer and 0 as the input buffer length. The AES-SIV implementation in OpenSSL just returns success for such a call instead of performing the associated data authentication operation. The empty data thus will not be authenticated. As this issue does not affect non-empty associated data authentication and we expect it to be rare for an application to use empty associated data entries this is qualified as Low severity issue. (CVE-2023-2975)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Answer 1

Hello Bobby33,

Thank you for your question and for reaching out with your question today.

It appears that you're dealing with multiple vulnerabilities in OpenSSL version 3.0.0 to 3.0.10 on Windows Server 2016 and 2019. You're asking whether Microsoft will issue a fix for these vulnerabilities.

Since OpenSSL is an open-source project maintained by the OpenSSL Software Foundation, Microsoft wouldn't directly issue a fix for vulnerabilities in OpenSSL itself. Instead, OpenSSL vulnerabilities would be patched by the OpenSSL project maintainers.

Here's what you can do:

1. Monitor OpenSSL Releases: Keep an eye on the official OpenSSL website for updates and new releases. The project maintainers regularly release security updates to address vulnerabilities. If a new version of OpenSSL is released (such as 3.0.10), it's advisable to update to the fixed version as soon as possible.
2. Apply Patches: If you're responsible for the systems running the vulnerable version of OpenSSL, apply any patches or updates provided by OpenSSL to address the vulnerabilities. Follow the recommended update procedures and make sure to thoroughly test the updated version in your environment before deploying it to production.
3. Check Vendor Updates: Some software products, including operating systems like Windows Server, bundle OpenSSL libraries. If you're using a version of Windows Server that includes OpenSSL libraries, check for updates provided by Microsoft. They might release updates that include patched versions of OpenSSL to address known vulnerabilities.
4. Mitigate Risks: If you're unable to update OpenSSL immediately, consider implementing mitigation strategies to reduce the impact of the vulnerabilities. This might involve isolating vulnerable systems, implementing network-level controls, or adjusting application configurations to minimize exposure.
5. Vulnerability Management: Implement a comprehensive vulnerability management program to identify, assess, and address vulnerabilities in your environment on an ongoing basis.

Remember that security vulnerabilities should be taken seriously, and prompt action should be taken to address them. Keeping software up to date and following security best practices is crucial for maintaining the security of your systems and data.

I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.

If the reply was helpful, please don’t forget to upvote or accept as answer.

Best regards.