CVE-2018-9256: Input Validation

Published Apr 4, 2018
·
Updated

In Wireshark 2.4.0 to 2.4.5 and 2.2.0 to 2.2.13, the LWAPP dissector could crash. This was addressed in epan/dissectors/packet-lwapp.c by limiting the encapsulation levels to restrict the recursion depth.

Affected Software

3 affected components
Wireshark Wireshark>=2.2.0<=2.2.13
Wireshark Wireshark>=2.4.0<=2.4.5
Debian Debian Linux=8.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Apply the change in epan/dissectors/packet-lwapp.c that limits LWAPP encapsulation levels to restrict recursion depth (fixes crashes in Wireshark 2.4.0–2.4.5 and 2.2.0–2.2.13).

    Wireshark (epan/dissectors/packet-lwapp.c) LWAPP encapsulation levels (recursion depth limit) = Limit encapsulation levels to restrict recursion depth

Event History

Apr 4, 2018
CVE Published
via MITRE·07:00 AM
Data Sourced
via MITRE·07:00 AM
Description
Data Sourced
via NVD·07:29 AM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2018-9256?

CVE-2018-9256 has a medium severity rating as it can cause Wireshark to crash due to a recursion depth issue in the LWAPP dissector.

2

How do I fix CVE-2018-9256?

To remediate CVE-2018-9256, update Wireshark to version 2.4.6 or later, or to version 2.2.14 or later.

3

What versions of Wireshark are affected by CVE-2018-9256?

Wireshark versions from 2.4.0 to 2.4.5 and from 2.2.0 to 2.2.13 are vulnerable to CVE-2018-9256.

4

What causes the crash in CVE-2018-9256?

The crash in CVE-2018-9256 is caused by an excessive recursion depth in the LWAPP dissector.

5

Is CVE-2018-9256 applicable to Debian users?

Yes, Debian users running the affected versions of Wireshark are at risk due to CVE-2018-9256.

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