Bug 1607331 (CVE-2018-14370) - CVE-2018-14370 wireshark: IEEE dissector infinite loop (wnpa-sec-2018-43)
Summary: CVE-2018-14370 wireshark: IEEE dissector infinite loop (wnpa-sec-2018-43)
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2018-14370
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: 1607333 1607334
Blocks: 1607335
TreeView+ depends on / blocked
 
Reported: 2018-07-23 09:55 UTC by Andrej Nemec
Modified: 2021-02-16 23:55 UTC (History)
7 users (show)

Fixed In Version: wireshark 2.6.2, wireshark 2.4.8, wireshark 2.2.16
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-08-07 20:10:11 UTC
Embargoed:

Attachments (Terms of Use)

Description Andrej Nemec 2018-07-23 09:55:13 UTC 
It was found that IEEE dissector could crash by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file.

Upstream bug(s):

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14686

External References:

https://www.wireshark.org/security/wnpa-sec-2018-43.html
Comment 1 Andrej Nemec 2018-07-23 09:58:14 UTC 
Created wireshark tracking bugs for this issue:

Affects: fedora-all [bug 1607334]
Comment 3 Pedro Yóssis Silva Barbosa 2018-08-07 20:10:11 UTC 
The wireshark shipped in Red Hat Enterprise Linux 6 and 7 do not have the dot11crypt traffic recognition functionality.

$ tshark -Vxr clusterfuzz-testcase-minimized-fuzzshark_ip_proto-udp-5122206420959232.pcap
tshark: The file "clusterfuzz-testcase-minimized-fuzzshark_ip_proto-udp-5122206420959232.pcap" contains record data that TShark doesn't support.
(pcap: network type 252 unknown or unsupported)
Comment 4 Pedro Yóssis Silva Barbosa 2018-08-07 20:10:26 UTC 
Statement:

This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 6 and 7 (versions 1.8.10 and 1.10.14, respectively).
Note You need to log in before you can comment on or make changes to this bug.