CVE-2018-7336: Null Pointer Dereference
Published Feb 23, 2018
·Updated
In Wireshark 2.4.0 to 2.4.4 and 2.2.0 to 2.2.12, the FCP protocol dissector could crash. This was addressed in epan/dissectors/packet-fcp.c by checking for a NULL pointer.
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
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2018-7336?
CVE-2018-7336 has a medium severity level as it can cause a crash of the Wireshark application.
2
How do I fix CVE-2018-7336?
To fix CVE-2018-7336, upgrade Wireshark to version 2.4.5 or later for 2.4.x series or 2.2.13 or later for 2.2.x series.
3
Which versions of Wireshark are affected by CVE-2018-7336?
CVE-2018-7336 affects Wireshark versions from 2.4.0 to 2.4.4 and 2.2.0 to 2.2.12.
4
Can CVE-2018-7336 be exploited remotely?
CVE-2018-7336 cannot be exploited remotely as it requires a local environment to trigger the crash.
5
Is there a workaround for CVE-2018-7336?
There are no known workarounds for CVE-2018-7336; the recommended solution is to update to a secure version.