CVE-2018-5335 : What You Need to Know

Wireshark versions 2.4.0 to 2.4.3 and 2.2.0 to 2.2.11 were affected by a crash issue in the WCP dissector, which has been resolved by implementing a buffer length validation check.

Understanding CVE-2018-5335

This CVE entry addresses a vulnerability in Wireshark versions 2.4.0 to 2.4.3 and 2.2.0 to 2.2.11 that could lead to a crash.

What is CVE-2018-5335?

In Wireshark versions 2.4.0 to 2.4.3 and 2.2.0 to 2.2.11, a vulnerability in the WCP dissector could cause the application to crash. The issue was fixed by adding a validation check on the buffer length in the epan/dissectors/packet-wcp.c file.

The Impact of CVE-2018-5335

The vulnerability could be exploited by an attacker to crash Wireshark, potentially leading to a denial of service condition.

Technical Details of CVE-2018-5335

Wireshark versions 2.4.0 to 2.4.3 and 2.2.0 to 2.2.11 were affected by this vulnerability.

Vulnerability Description

The crash issue in Wireshark was caused by a lack of validation on the buffer length in the WCP dissector.

Affected Systems and Versions

Wireshark versions 2.4.0 to 2.4.3
Wireshark versions 2.2.0 to 2.2.11

Exploitation Mechanism

An attacker could exploit this vulnerability by sending a specially crafted packet to the Wireshark application, triggering the crash.

Mitigation and Prevention

To address CVE-2018-5335, follow these steps:

Immediate Steps to Take

Update Wireshark to the latest version that includes the fix.
Monitor vendor advisories for any additional security recommendations.

Long-Term Security Practices

Regularly update Wireshark and other software to patch known vulnerabilities.
Implement network segmentation to limit the impact of potential attacks.

Patching and Updates

Apply patches provided by Wireshark promptly to ensure the security of the application.