Bug 1007192 (CVE-2013-5720) - CVE-2013-5720 wireshark: RTPS dissector crash (wnpa-sec-2013-57)
Summary: CVE-2013-5720 wireshark: RTPS dissector crash (wnpa-sec-2013-57)
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2013-5720
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1007254 1007261 1007278
Blocks: 1007214
TreeView+ depends on / blocked
 
Reported: 2013-09-12 05:35 UTC by Murray McAllister
Modified: 2021-02-17 07:21 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-13 04:44:13 UTC
Embargoed:


Attachments (Terms of Use)

Description Murray McAllister 2013-09-12 05:35:23 UTC
Ben Schmidt discovered a buffer overflow flaw in the Wireshark RTPS dissector. Wireshark could crash if it read a malformed packet off a network, or opened a malicious dump file. This issue affects Wireshark versions 1.10.0 to 1.10.1 and 1.8.0 to 1.8.9. It is fixed in versions 1.10.2 and 1.8.10.

References:

https://www.wireshark.org/security/wnpa-sec-2013-57.html

Comment 1 Murray McAllister 2013-09-12 08:14:03 UTC
Created wireshark tracking bugs for this issue:

Affects: fedora-all [bug 1007261]

Comment 3 Huzaifa S. Sidhpurwala 2013-09-13 04:20:51 UTC
Upstream bug: https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9019 (currently closed)

Patch: http://anonsvn.wireshark.org/viewvc?view=revision&revision=51213

Comment 4 Huzaifa S. Sidhpurwala 2013-09-13 04:21:32 UTC
Statement:

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

Comment 5 Huzaifa S. Sidhpurwala 2013-09-13 04:44:13 UTC
This issue affects the version of wireshark as shipped with Fedora 18 and 19.

Comment 8 Huzaifa S. Sidhpurwala 2014-01-21 13:33:39 UTC
I dont have access to the closed bug or the cap file, so this one will need to be SanityOnly


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