Bug 1045363 (CVE-2013-6449) - CVE-2013-6449 openssl: crash when using TLS 1.2 caused by use of incorrect hash algorithm
Summary: CVE-2013-6449 openssl: crash when using TLS 1.2 caused by use of incorrect ha...
Status: CLOSED ERRATA
Alias: CVE-2013-6449
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard: impact=important,public=20131219,repo...
Keywords: Security
Depends On: 1045211 1045441 1045443 1045444 1045459
Blocks: 1045440
TreeView+ depends on / blocked
 
Reported: 2013-12-20 09:28 UTC by Tomas Hoger
Modified: 2019-06-08 19:50 UTC (History)
18 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2014-01-08 20:09:50 UTC


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2014:0015 normal SHIPPED_LIVE Important: openssl security update 2014-01-08 23:16:14 UTC
Red Hat Product Errata RHSA-2014:0041 normal SHIPPED_LIVE Important: rhev-hypervisor6 security update 2014-01-21 22:02:59 UTC

Description Tomas Hoger 2013-12-20 09:28:44 UTC
A flaw was reported for OpenSSL 1.0.1e, that can cause application using OpenSSL to crash when using TLS version 1.2.  Issue was reported via the following OpenSSL upstream ticket:

http://rt.openssl.org/Ticket/Display.html?id=3200&user=guest&pass=guest

and also as bug for Apache Traffic Server:

https://issues.apache.org/jira/browse/TS-2355

Fix is now committed in upstream git:

http://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=ca98926

Related to the above ticket, upstream also added this fix to improve error checks in OpenSSL:

http://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=0294b2b

Comment 1 Tomas Hoger 2013-12-20 12:23:52 UTC
Support for TLS 1.2 in openssl packages in Red Hat Enterprise Linux 6 was only introduced in Red Hat Enterprise Linux 6.5, when openssl packages were updated from version 1.0.0 to 1.0.1e via RHBA-2013:1585.  The openssl packages in Red Hat Enterprise Linux 6 before 6.5 and earlier versions of Red Hat Enterprise Linux do not support TLS 1.1 and 1.2.

https://rhn.redhat.com/errata/RHBA-2013-1585.html

Comment 3 Tomas Hoger 2013-12-20 12:33:18 UTC
Created openssl tracking bugs for this issue:

Affects: fedora-all [bug 1045443]

Comment 4 Tomas Hoger 2013-12-20 12:33:21 UTC
Created mingw-openssl tracking bugs for this issue:

Affects: fedora-all [bug 1045444]

Comment 7 Fedora Update System 2013-12-22 05:32:16 UTC
openssl-1.0.1e-36.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2013-12-22 05:38:35 UTC
openssl-1.0.1e-36.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2013-12-22 05:39:30 UTC
openssl-1.0.1e-36.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Tomas Hoger 2014-01-07 19:45:03 UTC
Issue was fixed in upstream version 1.0.1f:

http://www.openssl.org/news/vulnerabilities.html#2013-6449
http://www.openssl.org/news/openssl-1.0.1-notes.html

Comment 11 Tomas Hoger 2014-01-07 19:46:00 UTC
Statement:

This issue did not affect the versions of openssl as shipped with Red Hat Enterprise Linux 5 and earlier.

Comment 12 errata-xmlrpc 2014-01-08 18:19:27 UTC
This issue has been addressed in following products:

  Red Hat Enterprise Linux 6

Via RHSA-2014:0015 https://rhn.redhat.com/errata/RHSA-2014-0015.html

Comment 13 Tomas Hoger 2014-01-08 20:51:28 UTC
Additional details form upstream developer, explaining 0.9.8 versions are unaffected:

http://www.mail-archive.com/openssl-dev@openssl.org/msg33547.html

Comment 14 errata-xmlrpc 2014-01-21 17:03:47 UTC
This issue has been addressed in following products:

  RHEV-H and Agents for RHEL-6

Via RHSA-2014:0041 https://rhn.redhat.com/errata/RHSA-2014-0041.html


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