| Max CVSS | 7.8 | Min CVSS | 5.0 | Total Count | 2 |
| ID | CVSS | Summary | Last (major) update | Published | |
| CVE-2017-7700 | 7.1 |
In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the NetScaler file parser could go into an infinite loop, triggered by a malformed capture file. This was addressed in wiretap/netscaler.c by ensuring a nonzero record size.
|
03-10-2019 - 00:03 | 12-04-2017 - 23:59 | |
| CVE-2017-7702 | 7.8 |
In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the WBXML dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-wbxml.c by adding length validation.
|
03-10-2019 - 00:03 | 12-04-2017 - 23:59 | |
| CVE-2017-7705 | 7.8 |
In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the RPC over RDMA dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-rpcrdma.c by correctly checking for g
|
03-10-2019 - 00:03 | 12-04-2017 - 23:59 | |
| CVE-2017-6014 | 7.8 |
In Wireshark 2.2.4 and earlier, a crafted or malformed STANAG 4607 capture file will cause an infinite loop and memory exhaustion. If the packet size field in a packet header is null, the offset to read from will not advance, causing continuous attem
|
03-10-2019 - 00:03 | 17-02-2017 - 07:59 | |
| CVE-2017-7704 | 7.8 |
In Wireshark 2.2.0 to 2.2.5, the DOF dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-dof.c by using a different integer data type and adjusting a return
|
03-10-2019 - 00:03 | 12-04-2017 - 23:59 | |
| CVE-2017-7701 | 7.8 |
In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the BGP dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-bgp.c by using a different integer data type.
|
03-10-2019 - 00:03 | 12-04-2017 - 23:59 | |
| CVE-2017-7703 | 5.0 |
In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the IMAP dissector could crash, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-imap.c by calculating a line's end correctly.
|
01-03-2019 - 12:45 | 12-04-2017 - 23:59 |