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

23 affected componentsFixes available
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
alpine/wireshark>=2.2.0<2.4.5-r0
2.4.5-r0
alpine/wireshark>=2.2.0<2.4.5-r0
2.4.5-r0
alpine/wireshark>=2.2.0<2.4.5-r0
2.4.5-r0
alpine/wireshark>=2.2.0<2.4.5-r0
2.4.5-r0
alpine/wireshark>=2.2.0<2.4.5-r0
2.4.5-r0
alpine/wireshark>=2.2.0<2.4.5-r0
2.4.5-r0
alpine/wireshark>=2.2.0<2.4.5-r0
2.4.5-r0
alpine/wireshark>=2.2.0<2.4.5-r0
2.4.5-r0
alpine/wireshark>=2.2.0<2.4.5-r0
2.4.5-r0
alpine/wireshark>=2.2.0<2.4.5-r0
2.4.5-r0
alpine/wireshark>=2.2.0<2.4.5-r0
2.4.5-r0
alpine/wireshark>=2.2.0<2.4.5-r0
2.4.5-r0
alpine/wireshark>=2.2.0<2.4.5-r0
2.4.5-r0
alpine/wireshark>=2.2.0<2.4.5-r0
2.4.5-r0
alpine/wireshark>=2.2.0<2.4.5-r0
2.4.5-r0
alpine/wireshark>=2.2.0<2.2.15-r0
2.2.15-r0
alpine/wireshark>=2.2.0<2.4.5-r0
2.4.5-r0
alpine/wireshark>=2.2.0<2.4.5-r0
2.4.5-r0
alpine/wireshark>=2.2.0<2.4.5-r0
2.4.5-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade alpine/wireshark to a version that resolves this vulnerability.

    Fixed in 2.4.5-r0
  2. Upgrade

    Upgrade alpine/wireshark to a version that resolves this vulnerability.

    Fixed in 2.2.15-r0

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
Data Sourced
via OSV·10:29 PM
DescriptionSeverityAffected 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.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203