Bug 862508 - (CVE-2012-5239) CVE-2012-5239 wireshark: Infinite loop in the DRDA dissector
CVE-2012-5239 wireshark: Infinite loop in the DRDA dissector
Status: CLOSED DUPLICATE of bug 849926
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
: Security
Depends On: 862530
Blocks: 862511
  Show dependency treegraph
Reported: 2012-10-03 01:28 EDT by Huzaifa S. Sidhpurwala
Modified: 2016-03-04 06:34 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-10-03 04:21:22 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Huzaifa S. Sidhpurwala 2012-10-03 01:28:10 EDT
An infinite loop was found in the way Distributed Relational Database Architecture (DRDA) dissector of the Wireshark network traffic analyzer processed certain capture files. If Wireshark read a malformed packet off a network or opened a malicious packet capture file, it could lead to denial of service (Wireshark hang).

Upstream advisory: http://www.wireshark.org/security/wnpa-sec-2012-28.html
Bug report: https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7666
Patch: http://anonsvn.wireshark.org/viewvc?view=revision&revision=44749
Comment 1 Huzaifa S. Sidhpurwala 2012-10-03 02:57:30 EDT

This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6.
Comment 2 Huzaifa S. Sidhpurwala 2012-10-03 02:57:48 EDT
This issue affects the version of wireshark as shipped with Fedora 16 and Fedora 17.
Comment 3 Huzaifa S. Sidhpurwala 2012-10-03 03:08:28 EDT
Created wireshark tracking bugs for this issue

Affects: fedora-all [bug 862530]
Comment 4 Huzaifa S. Sidhpurwala 2012-10-03 04:21:22 EDT

*** This bug has been marked as a duplicate of bug 849926 ***

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