In Wireshark 2.2.0 to 2.2.5, the DOF dissector could go...
High severity
Unreviewed
Published
May 13, 2022
to the GitHub Advisory Database
•
Updated Feb 2, 2023
Description
Published by the National Vulnerability Database
Apr 12, 2017
Published to the GitHub Advisory Database
May 13, 2022
Last updated
Feb 2, 2023
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.
References