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.

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.

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.

Can CVE-2018-7336 be exploited remotely?

CVE-2018-7336 cannot be exploited remotely as it requires a local environment to trigger the crash.

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.

Vulnerability/
CVE-2018-7336

high

7.5

CWE

476

23/2/2018

5/8/2024

CVE-2018-7336: Null Pointer Dereference

First published: Fri 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.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Wireshark Wireshark	>=2.2.0<=2.2.12
Wireshark Wireshark	>=2.4.0<=2.4.4
Debian GNU/Linux	=7.0
Debian GNU/Linux	=8.0

Remedy

https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=b56f598f1bc04f5d00f13b38c713763928cedb7c

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

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.
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.
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.
Can CVE-2018-7336 be exploited remotely?
CVE-2018-7336 cannot be exploited remotely as it requires a local environment to trigger the crash.
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.

agent/type
collector/mitre-cve
source/MITRE
agent/author
agent/severity
agent/weakness
agent/references
agent/last-modified-date
agent/remedy
agent/description
agent/first-publish-date
agent/event
agent/source
agent/softwarecombine
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/wireshark
canonical/wireshark wireshark
version/wireshark wireshark/2.2.0
version/wireshark wireshark/2.2.12
version/wireshark wireshark/2.4.0
version/wireshark wireshark/2.4.4
vendor/debian
canonical/debian gnu/linux
version/debian gnu/linux/7.0
version/debian gnu/linux/8.0

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.

Frequently Asked Questions

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.
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.
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.
Can CVE-2018-7336 be exploited remotely?
CVE-2018-7336 cannot be exploited remotely as it requires a local environment to trigger the crash.
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.