Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1411238 - openssl switches to (SHA1, RSA) if no usable signature algorithm is specified
openssl switches to (SHA1, RSA) if no usable signature algorithm is specified
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: openssl (Show other bugs)
7.3
All Linux
medium Severity medium
: rc
: ---
Assigned To: Tomas Mraz
Stefan Dordevic
: Reopened
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-01-09 03:48 EST by Stanislav Zidek
Modified: 2017-08-01 14:16 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-01 14:16:10 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1929 normal SHIPPED_LIVE openssl bug fix and enhancement update 2017-08-01 14:08:01 EDT

  None (edit)
Description Stanislav Zidek 2017-01-09 03:48:42 EST
Description of problem:
If client sends only (MD5, RSA) in signature algorithms in ClientHello (or any other combination not supported by the server), it uses (SHA1, RSA) by default. This violates RFC 5246 (see bz1410573 for further details).

Version-Release number of selected component (if applicable):
openssl-1.0.1e-60.el7

How reproducible:
always

Steps to Reproduce:
1. start s_server
2. send ClientHello containing only (MD5, RSA) signature algorithm
3. look at signature algorithm used in ServerKeyExchange

Actual results:
(SHA1, RSA) is used

Expected results:
Connection is aborted.

Additional info:
This is already fixed in openssl-1.0.2j-1.fc24
Comment 2 Tomas Mraz 2017-04-03 10:34:41 EDT

*** This bug has been marked as a duplicate of bug 1276310 ***
Comment 6 errata-xmlrpc 2017-08-01 14:16:10 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:1929

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