Bug 1127505 (CVE-2014-3512) - CVE-2014-3512 openssl: SRP buffer overrun
Summary: CVE-2014-3512 openssl: SRP buffer overrun
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2014-3512
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1127468 1127506
TreeView+ depends on / blocked
 
Reported: 2014-08-07 02:14 UTC by Andrew Griffiths
Modified: 2019-09-29 13:20 UTC (History)
61 users (show)

Fixed In Version: openssl 1.0.1i
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-07 06:01:29 UTC


Attachments (Terms of Use)

Description Andrew Griffiths 2014-08-07 02:14:37 UTC
It was found that OpenSSL applications set up for SRP could have an internal buffer overrun if a malicious server or client sent invalid SRP parameters.

Comment 1 Arun Babu Neelicattu 2014-08-07 05:52:57 UTC
External References:

https://www.openssl.org/news/secadv_20140806.txt

Comment 3 Tomas Hoger 2014-08-07 06:01:29 UTC
The openssl packages shipped in Red Hat Enterprise Linux and Fedora are build with the Secure Remote Password (SRP) support disabled and were therefore not affected by this issue.

Upstream commit:
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=4a23b12a031860253b58d503f296377ca076427b

Comment 5 Tomas Hoger 2014-08-07 06:31:01 UTC
Note that SRP support was introduced upstream in version 1.0.1.

https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=edc032b
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=0deea0e

Comment 6 David Jorm 2014-08-07 06:37:46 UTC
Statement:

Not vulnerable. This issue did not affect the versions of openssl as shipped
with Red Hat Enterprise Linux 5, 6 and 7, Red Hat Enterprise Virtualization 3,
and Red Hat Enterprise Storage 2, as they do not enable Secure Remote Password
(SRP) support. All other supported Red Hat products that include openssl use
older versions that are not affected by this issue.


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