Bug 1017983 (CVE-2013-4421) - CVE-2013-4421 dropbear: memory exhaustion DoS via large decompressed payloads
Summary: CVE-2013-4421 dropbear: memory exhaustion DoS via large decompressed payloads
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2013-4421
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: 1017985 1017986
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-10 22:08 UTC by Vincent Danen
Modified: 2019-09-29 13:09 UTC (History)
4 users (show)

Fixed In Version: dropbear 2013.59
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-04 08:55:54 UTC
Embargoed:


Attachments (Terms of Use)

Description Vincent Danen 2013-10-10 22:08:51 UTC
It was reported [1] that versions of dropbear prior to 2013.59 suffered from a flaw where large decompressed payloads could cause memory exhaustion, resulting in a denial of service.

This has been fixed in git [2].  A CVE assignment is pending [3].

[1] https://matt.ucc.asn.au/dropbear/CHANGES
[2] https://secure.ucc.asn.au/hg/dropbear/rev/0bf76f54de6f
[3] http://www.openwall.com/lists/oss-security/2013/10/10/15

Comment 1 Vincent Danen 2013-10-10 22:11:34 UTC
Created dropbear tracking bugs for this issue:

Affects: fedora-all [bug 1017985]
Affects: epel-all [bug 1017986]

Comment 2 Fedora Update System 2013-10-18 19:48:06 UTC
dropbear-2013.59-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 3 Fedora Update System 2013-10-18 19:53:12 UTC
dropbear-2013.59-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 4 Fedora Update System 2013-10-25 17:38:39 UTC
dropbear-2013.59-1.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.


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