M4ximuss (3)

Last Login: December 27, 2021
Assessments
1
Score
3

M4ximuss's Latest (1) Contributions

Sort by:
Filter by:
2
Ratings
Technical Analysis

This is a denial of service condition against unpatched Wireshark clients for Windows. From Wireshark website “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.” In other words, the worst case scenario is you crash Wireshark, and the user simply has to restart the client.

Solution is to upgrade to Wireshark 3.2.5 or later.