Read/write after SSL object in error state (CVE-2017-3737)
This document (7022626) is provided subject to the disclaimer at the end of this document.
Reflection Desktop 16.1 version 16.1.348 and earlier
InfoConnect Desktop 16.1 version 16.1.348 and earlier
OpenSSL 1.0.2 (starting from version 1.0.2b) introduced an "error state" mechanism. The intent was that if a fatal error occurred during a handshake then OpenSSL would move into the error state and would immediately fail if you attempted to continue the handshake. This works as designed for the explicit handshake functions (SSL_do_handshake(), SSL_accept() and SSL_connect()), however due to a bug it does not work correctly if SSL_read() or SSL_write() is called directly. In that scenario, if the handshake fails then a fatal error will be returned in the initial function call. If SSL_read()/SSL_write() is subsequently called by the application for the same SSL object then it will succeed and the data is passed without being decrypted/encrypted directly from the SSL/TLS record layer. In order to exploit this issue an application bug would have to be present that resulted in a call to SSL_read()/SSL_write() being issued after having already received a fatal error. OpenSSL version 1.0.2b-1.0.2m are affected. Fixed in OpenSSL 1.0.2n. OpenSSL 1.1.0 is not affected.
This issue is addressed in Reflection/InfoConnect Desktop 16.1 version 16.1.362 and higher.
For vulnerability details, see the National Vulnerability Database:
This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7022626
- Creation Date:31-JAN-18
- Modified Date:01-JUN-18
- NovellInfoConnect DesktopReflection Desktop
Did this document solve your problem? Provide Feedback