Vulmon
Recent Vulnerabilities
Product List
Research Posts
Trends
Blog
About
Contact
Vulmon Alerts
By Relevance
By Risk Score
By Publish Date
wireshark wireshark vulnerabilities and exploits
(subscribe to this query)
694
VMScore
CVE-2017-9345
In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the DNS dissector could go into an infinite loop. This was addressed in epan/dissectors/packet-dns.c by trying to detect self-referencing pointers.
Wireshark Wireshark
694
VMScore
CVE-2017-9346
In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the SoulSeek dissector could go into an infinite loop. This was addressed in epan/dissectors/packet-slsk.c by making loop bounds more explicit.
Wireshark Wireshark
694
VMScore
CVE-2017-9350
In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the openSAFETY dissector could crash or exhaust system memory. This was addressed in epan/dissectors/packet-opensafety.c by checking for a negative length.
Wireshark Wireshark
694
VMScore
CVE-2017-9352
In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the Bazaar dissector could go into an infinite loop. This was addressed in epan/dissectors/packet-bzr.c by ensuring that backwards parsing cannot occur.
Wireshark Wireshark
694
VMScore
CVE-2017-7702
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.
Wireshark Wireshark 2.0.0
Wireshark Wireshark 2.0.4
Wireshark Wireshark 2.2.0
Wireshark Wireshark 2.0.9
Wireshark Wireshark 2.2.2
Wireshark Wireshark 2.0.1
Wireshark Wireshark 2.2.1
Wireshark Wireshark 2.2.4
Wireshark Wireshark 2.0.11
Wireshark Wireshark 2.0.7
Wireshark Wireshark 2.0.2
Wireshark Wireshark 2.0.8
Wireshark Wireshark 2.0.3
Wireshark Wireshark 2.2.5
Wireshark Wireshark 2.0.6
Wireshark Wireshark 2.0.10
Wireshark Wireshark 2.2.3
Wireshark Wireshark 2.0.5
694
VMScore
CVE-2017-7705
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...
Wireshark Wireshark 2.0.0
Wireshark Wireshark 2.0.4
Wireshark Wireshark 2.2.0
Wireshark Wireshark 2.0.9
Wireshark Wireshark 2.2.2
Wireshark Wireshark 2.0.1
Wireshark Wireshark 2.2.1
Wireshark Wireshark 2.2.4
Wireshark Wireshark 2.0.11
Wireshark Wireshark 2.0.7
Wireshark Wireshark 2.0.2
Wireshark Wireshark 2.0.8
Wireshark Wireshark 2.0.3
Wireshark Wireshark 2.2.5
Wireshark Wireshark 2.0.6
Wireshark Wireshark 2.0.10
Wireshark Wireshark 2.2.3
Wireshark Wireshark 2.0.5
694
VMScore
CVE-2017-7701
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.
Wireshark Wireshark 2.0.0
Wireshark Wireshark 2.0.4
Wireshark Wireshark 2.2.0
Wireshark Wireshark 2.0.9
Wireshark Wireshark 2.2.2
Wireshark Wireshark 2.0.1
Wireshark Wireshark 2.2.1
Wireshark Wireshark 2.2.4
Wireshark Wireshark 2.0.11
Wireshark Wireshark 2.0.7
Wireshark Wireshark 2.0.2
Wireshark Wireshark 2.0.8
Wireshark Wireshark 2.0.3
Wireshark Wireshark 2.2.5
Wireshark Wireshark 2.0.6
Wireshark Wireshark 2.0.10
Wireshark Wireshark 2.2.3
Wireshark Wireshark 2.0.5
694
VMScore
CVE-2017-7704
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 value.
Wireshark Wireshark 2.2.0
Wireshark Wireshark 2.2.2
Wireshark Wireshark 2.2.1
Wireshark Wireshark 2.2.4
Wireshark Wireshark 2.2.5
Wireshark Wireshark 2.2.3
694
VMScore
CVE-2017-7745
In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the SIGCOMP dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-sigcomp.c by correcting a memory-size check.
Wireshark Wireshark 2.0.0
Wireshark Wireshark 2.0.4
Wireshark Wireshark 2.2.0
Wireshark Wireshark 2.0.9
Wireshark Wireshark 2.2.2
Wireshark Wireshark 2.0.1
Wireshark Wireshark 2.2.1
Wireshark Wireshark 2.2.4
Wireshark Wireshark 2.0.11
Wireshark Wireshark 2.0.7
Wireshark Wireshark 2.0.2
Wireshark Wireshark 2.0.8
Wireshark Wireshark 2.0.3
Wireshark Wireshark 2.2.5
Wireshark Wireshark 2.0.6
Wireshark Wireshark 2.0.10
Wireshark Wireshark 2.2.3
Wireshark Wireshark 2.0.5
694
VMScore
CVE-2017-7748
In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the WSP dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-wsp.c by adding a length check.
Wireshark Wireshark 2.0.0
Wireshark Wireshark 2.0.4
Wireshark Wireshark 2.2.0
Wireshark Wireshark 2.0.9
Wireshark Wireshark 2.2.2
Wireshark Wireshark 2.0.1
Wireshark Wireshark 2.2.1
Wireshark Wireshark 2.2.4
Wireshark Wireshark 2.0.11
Wireshark Wireshark 2.0.7
Wireshark Wireshark 2.0.2
Wireshark Wireshark 2.0.8
Wireshark Wireshark 2.0.3
Wireshark Wireshark 2.2.5
Wireshark Wireshark 2.0.6
Wireshark Wireshark 2.0.10
Wireshark Wireshark 2.2.3
Wireshark Wireshark 2.0.5
VMScore
CVSSv2
CVSSv3
VMScore
Recommendations:
CVE-2024-27802
template injection
CVE-2024-0044
code injection
CVE-2024-35474
CVE-2024-27857
CVE-2024-23251
CVE-2024-23692
physical
Vulnerability Notification Service
You don’t have to wait for vulnerability scanning results
Get Started
« PREV
1
2
3
4
5
6
7
8
9
10
NEXT »