First published: Wed Apr 12 2017(Updated: )
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 going beyond the maximum offset.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Wireshark Wireshark | =2.0.0 | |
Wireshark Wireshark | =2.0.1 | |
Wireshark Wireshark | =2.0.2 | |
Wireshark Wireshark | =2.0.3 | |
Wireshark Wireshark | =2.0.4 | |
Wireshark Wireshark | =2.0.5 | |
Wireshark Wireshark | =2.0.6 | |
Wireshark Wireshark | =2.0.7 | |
Wireshark Wireshark | =2.0.8 | |
Wireshark Wireshark | =2.0.9 | |
Wireshark Wireshark | =2.0.10 | |
Wireshark Wireshark | =2.0.11 | |
Wireshark Wireshark | =2.2.0 | |
Wireshark Wireshark | =2.2.1 | |
Wireshark Wireshark | =2.2.2 | |
Wireshark Wireshark | =2.2.3 | |
Wireshark Wireshark | =2.2.4 | |
Wireshark Wireshark | =2.2.5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.