Bug 1127502 (CVE-2014-3507) - CVE-2014-3507 openssl: DTLS memory leak from zero-length fragments
Summary: CVE-2014-3507 openssl: DTLS memory leak from zero-length fragments
Keywords:
Status: NEW
Alias: CVE-2014-3507
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: 1127695 1127696 1127697 1127698 1127704 1127705 1127709 1128405 1128406 1128961 1181611
Blocks: 1127468 1127506
TreeView+ depends on / blocked
 
Reported: 2014-08-07 02:06 UTC by Andrew Griffiths
Modified: 2019-09-29 13:20 UTC (History)
49 users (show)

Fixed In Version: openssl 1.0.1i, openssl 1.0.0n, openssl 0.9.8zb
Doc Type: Bug Fix
Doc Text:
A flaw was discovered in the way OpenSSL handled DTLS packets. A remote attacker could use this flaw to cause a DTLS server or client using OpenSSL to crash or use excessive amounts of memory.
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2014:1052 normal SHIPPED_LIVE Moderate: openssl security update 2014-08-14 01:32:03 UTC
Red Hat Product Errata RHSA-2014:1054 normal SHIPPED_LIVE Moderate: openssl security update 2014-08-14 08:44:38 UTC

Description Andrew Griffiths 2014-08-07 02:06:15 UTC
It was found that an attacker could force OpenSSL to leak memory and never free it via DTLS packets.

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

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

Comment 5 Tomas Hoger 2014-08-07 11:33:27 UTC
Created openssl tracking bugs for this issue:

Affects: fedora-all [bug 1127704]

Comment 6 Tomas Hoger 2014-08-07 11:33:32 UTC
Created mingw-openssl tracking bugs for this issue:

Affects: fedora-all [bug 1127705]

Comment 7 Tomas Hoger 2014-08-07 11:39:26 UTC
Created mingw-openssl tracking bugs for this issue:

Affects: epel-7 [bug 1127709]

Comment 8 Tomas Hoger 2014-08-07 14:33:10 UTC
This did not affect openssl packages in Red Hat Enterprise Linux 5 (based on upstream 0.9.8e) and openssl 1.0.0 packages in Red Hat Enterprise Linux 6 (i.e. packages released before RHBA-2013:1585, which rebased openssl from 1.0.0 to 1.0.1e).  Issue was introduced upstream in versions 0.9.8o and 1.0.0a via the following change:

https://rt.openssl.org/Ticket/Display.html?id=2230&user=guest&pass=guest
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=c713a4c
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=1507f3a

Comment 9 Fedora Update System 2014-08-09 07:34:38 UTC
openssl-1.0.1e-39.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 Fedora Update System 2014-08-09 07:35:47 UTC
openssl-1.0.1e-39.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 12 Martin Prpič 2014-08-12 07:42:58 UTC
IssueDescription:

A flaw was discovered in the way OpenSSL handled DTLS packets. A remote attacker could use this flaw to cause a DTLS server or client using OpenSSL to crash or use excessive amounts of memory.

Comment 13 errata-xmlrpc 2014-08-13 21:33:40 UTC
This issue has been addressed in following products:

  Red Hat Enterprise Linux 6
  Red Hat Enterprise Linux 7

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

Comment 14 errata-xmlrpc 2014-08-14 04:45:10 UTC
This issue has been addressed in following products:

  Red Hat Storage 2.1

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

Comment 15 Vincent Danen 2014-08-20 14:38:31 UTC
Statement:

This did not affect openssl packages in Red Hat Enterprise Linux 5 (based on upstream 0.9.8e) and openssl 1.0.0 packages in Red Hat Enterprise Linux 6 (i.e. packages released before RHBA-2013:1585, which rebased openssl from 1.0.0 to 1.0.1e).  The issue was introduced upstream in versions 0.9.8o and 1.0.0a.


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