CVE-2018-7418: High severity Wireshark Wireshark vulnerability
Published Feb 23, 2018
·Updated
In Wireshark 2.2.0 to 2.2.12 and 2.4.0 to 2.4.4, the SIGCOMP dissector could crash. This was addressed in epan/dissectors/packet-sigcomp.c by correcting the extraction of the length value.
Affected Software
4 affected components
Wireshark Wireshark>=2.2.0<=2.2.12
Wireshark Wireshark>=2.4.0<=2.4.4
Debian Debian Linux=7.0
Debian Debian Linux=8.0
Remediation
Event History
Feb 23, 2018
CVE Published
via MITRE·10:00 PM
Data Sourced
via MITRE·10:00 PM
Description
Data Sourced
via NVD·10:29 PM
DescriptionSeverityAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2018-7418?
The severity of CVE-2018-7418 is classified as medium due to the potential for a crash in Wireshark.
2
How do I fix CVE-2018-7418?
To fix CVE-2018-7418, upgrade Wireshark to the latest version available beyond 2.4.4 or 2.2.12.
3
What versions of Wireshark are affected by CVE-2018-7418?
Wireshark versions from 2.2.0 to 2.2.12 and from 2.4.0 to 2.4.4 are affected by CVE-2018-7418.
4
What component of Wireshark is vulnerable in CVE-2018-7418?
The SIGCOMP dissector in Wireshark is the vulnerable component addressed in CVE-2018-7418.
5
Can CVE-2018-7418 lead to data loss?
CVE-2018-7418 may cause application instability but does not directly lead to data loss.