Bug 906331 (CVE-2013-1575) - CVE-2013-1575 wireshark: Infinite loop in the R3 dissector (wnpa-sec-2013-01, bug 8040)
Summary: CVE-2013-1575 wireshark: Infinite loop in the R3 dissector (wnpa-sec-2013-01,...
Alias: CVE-2013-1575
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 906387
Blocks: 906403
TreeView+ depends on / blocked
Reported: 2013-01-31 13:33 UTC by Jan Lieskovsky
Modified: 2021-02-17 08:09 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-02-04 05:35:50 UTC

Attachments (Terms of Use)

Description Jan Lieskovsky 2013-01-31 13:33:41 UTC
A denial of service flaw was found in the way R3 dissector of Wireshark, a network traffic analyzer, performed dissection of certain R3 packet capture files. A remote attacker could provide a specially-crafted R3 packet / packet capture that, when processed, would lead to excessive CPU consumption or into situation where tshark executable would enter an infinite loop, when trying to process the crafted packet / packet capture file.

Upstream bug report:
[1] https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8040

Sample packet capture:
[2] https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8040#c0

Relevant upstream patches:
[3] http://anonsvn.wireshark.org/viewvc?view=revision&revision=46415
[4] http://anonsvn.wireshark.org/viewvc?view=revision&revision=46416
[5] http://anonsvn.wireshark.org/viewvc?view=revision&revision=46417

[6] http://www.wireshark.org/security/wnpa-sec-2013-01.html
[7] http://www.openwall.com/lists/oss-security/2013/01/31/2

Comment 1 Jan Lieskovsky 2013-01-31 14:54:12 UTC
Created wireshark tracking bugs for this issue

Affects: fedora-all [bug 906387]

Comment 2 Huzaifa S. Sidhpurwala 2013-02-04 05:17:13 UTC

Not Vulnerable. This issue does not affect the version of wireshark as shipped with Red Hat Enterprise Linux 5 and 6.

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