Red Hat Bugzilla – Bug 233599
Stricter SSL session ID matching.
Last modified: 2011-12-12 21:44:57 EST
The following was committed to OpenSSL
+ *) In the SSL/TLS server implementation, be strict about session ID
+ context matching (which matters if an application uses a single
+ external cache for different purposes). Previously,
+ out-of-context reuse was forbidden only if SSL_VERIFY_PEER was
+ set. This did ensure strict client verification, but meant that,
+ with applications using a single external cache for quite
+ different requirements, clients could circumvent ciphersuite
+ restrictions for a given session ID context by starting a session
+ in a different context.
+ [Bodo Moeller]
Apache HTTP server uses a single session cache shared across multiple virtual
hosts. If client certificates are not in use, this issue could allow a session
to be resumed on a different vhost of the server from which it was originated,
bypassing any more restrictive checks that are performed during initial session
negotiation (such as checking cipher type or strength).
Marking as low severity and deferring because this is an uncommon configuration
with minimal consequences and is behaving as documented in Apache docs.
Given it's low impact, the decision was taken to move this to 5.2.
This issue is an issue we've deferred; therefore it should only get included if
we need to do OpenSSL updates for some other reason (for example a security
issue of severity > low, or bug fixes as part of an Update release).
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.