Bug 1036840 - disable weak (LOW and EXP) ciphers by default when using SSL_CTX_new(SSLv23*_method())
Summary: disable weak (LOW and EXP) ciphers by default when using SSL_CTX_new(SSLv23*_...
Keywords:
Status: CLOSED DUPLICATE of bug 1057520
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: openssl
Version: 6.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: beta
: ---
Assignee: Tomas Mraz
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-02 18:01 UTC by David Jaša
Modified: 2014-03-20 13:52 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-20 13:52:50 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description David Jaša 2013-12-02 18:01:04 UTC
Description of problem:
When creating a SSL context using one of SSLv23_*method(), openssl permits also weak ciphers (LOW and EXP groups). These ciphers are obsolete for really long time and they should not be used unless explicitly enabled.

Version-Release number of selected component (if applicable):
openssl-1.0.1e-15.el6.x86_64

How reproducible:
always

Steps to Reproduce:
server:
1. set up an openssl-based server with no cipher/tls version preference
2. connect to the server with "openssl s_client <...> -cipher 'LOW:EXP'" (or testing tools from gnutls or nss set to just weak ciphers)

client:
1. run "openssl s_server ... -cipher 'EXP:LOW'"
2. connect to the server with unsuspecting openssl-based client that uses just SSL_CTX_new(SSLv23_method())

Actual results:
connection is established in both cases

Expected results:
connection should fail unless the weak cipher suites are explicitly enabled

Additional info:

Comment 1 Tomas Mraz 2013-12-02 21:35:23 UTC
I'm sorry but this is a kind of thing we cannot do in released version of RHEL.

We could still do this in RHEL-7, but even there it needs serious reasoning.

Comment 2 Tomas Mraz 2014-03-20 13:52:50 UTC

*** This bug has been marked as a duplicate of bug 1057520 ***


Note You need to log in before you can comment on or make changes to this bug.