Wireshark reports:
It may be possible to make Wireshark crash by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file.
It may be possible to make Wireshark consume excessive CPU resources by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file.
The PPP dissector could crash.
The NFS dissector could use excessive amounts of CPU.
The DCP ETSI dissector could trigger a zero division.
The MongoDB dissector could go into a large loop.
The XTP dissector could go into an infinite loop.
The ERF dissector could overflow a buffer.
The AFP dissector could go into a large loop.
The RTPS2 dissector could overflow a buffer.
The GSM RLC MAC dissector could overflow a buffer.
The CIP dissector could exhaust system memory.
The STUN dissector could crash.
The EtherCAT Mailbox dissector could abort.
The CTDB dissector could go into a large loop.
The pcap-ng file parser could trigger a zero division.
The Ixia IxVeriWave file parser could overflow a buffer.
Disclaimer: The data contained on this page is derived from the VuXML document, please refer to the the original document for copyright information. The author of portaudit makes no claim of authorship or ownership of any of the information contained herein.
If you have found a vulnerability in a FreeBSD port not listed in the database, please contact the FreeBSD Security Team. Refer to "FreeBSD Security Information" for more information.