Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
7.5

CVE-2020-25862: Wireshark may crash when processing malformed TCP checksum

CVE-2020-25862 · published 6 years ago
Summary

Versions of Wireshark (2.6.0-2.6.20, 3.0.0-3.0.13, and 3.2.0-3.2.6) can stop working if they encounter a TCP packet with an invalid checksum value of 0xFFFF. This could cause the application to close unexpectedly, interrupting network analysis. Updating Wireshark to a newer version that corrects this handling will prevent the crash.

What to do
  • Update debian wireshark to version 3.2.7-1.
Affected software
Ecosystem VendorProductAffected versions
Debian:12 debian wireshark < 3.2.7-1
Fix: upgrade to 3.2.7-1
Debian:13 debian wireshark < 3.2.7-1
Fix: upgrade to 3.2.7-1
Debian:14 debian wireshark < 3.2.7-1
Fix: upgrade to 3.2.7-1
– wireshark wireshark >= 2.6.0, <= 2.6.20
>= 3.0.0, <= 3.0.13
>= 3.2.0, <= 3.2.6
cpe:2.3:a:wireshark:wireshark:*:*:*:*:*:*:*:*
– fedoraproject fedora 31
32
33
cpe:2.3:o:fedoraproject:fedora:31:*:*:*:*:*:*:*
– opensuse leap 15.1
15.2
cpe:2.3:o:opensuse:leap:15.1:*:*:*:*:*:*:*
– debian debian_linux 9.0
cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*
– oracle zfs_storage_appliance_firmware 8.8
cpe:2.3:o:oracle:zfs_storage_appliance_firmware:8.8:*:*:*:*:*:*:*
Original advisory text
In Wireshark 3.2.0 to 3.2.6, 3.0.0 to 3.0.13, and 2.6.0 to 2.6.20, the TCP dissector could crash. This was addressed in epan/dissectors/packet-tcp.c by changing the handling of the invalid 0xFFFF c...
In Wireshark 3.2.0 to 3.2.6, 3.0.0 to 3.0.13, and 2.6.0 to 2.6.20, the TCP dissector could crash. This was addressed in epan/dissectors/packet-tcp.c by changing the handling of the invalid 0xFFFF checksum.
Severity
7.5 High
Exploitation
2% chance of attack within 30 days
Type
CWE-354Improper Validation of Integrity Check Value
Timeline
Published6 Oct 2020
Updated29 Oct 2026
First seen11 Sep 2026
Sources
CVE-2020-25862 · NVD
Track software like this
Free during beta