Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
7.5

Wireshark may crash when processing certain LDSS data

CVE-2018-11362 · published 8 years ago
Summary

Versions 2.2.0‑2.2.14, 2.4.0‑2.4.6 and 2.6.0 of Wireshark can stop working if they encounter LDSS network traffic that is missing a required end‑of‑string marker. The problem was fixed by changing the code so it no longer reads past the end of the data. Upgrade to a newer Wireshark release or apply the available patch to avoid the crash.

What to do

The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.

Affected software
VendorProductAffected versions
wireshark wireshark >= 2.2.0, <= 2.2.14
>= 2.4.0, <= 2.4.6
2.6.0
cpe:2.3:a:wireshark:wireshark:*:*:*:*:*:*:*:*
debian debian_linux 7.0
8.0
9.0
cpe:2.3:o:debian:debian_linux:7.0:*:*:*:*:*:*:*
Original advisory text
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the LDSS dissector could crash. This was addressed in epan/dissectors/packet-ldss.c by avoiding a buffer over-read upon encountering a missi...
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the LDSS dissector could crash. This was addressed in epan/dissectors/packet-ldss.c by avoiding a buffer over-read upon encountering a missing '\0' character.
References
Fix within
Internet-facing 14 days
Internal 60 days
  • Not known to be exploited
  • Can be exploited automatically (estimated)
  • Gives an attacker partial control (estimated)
Severity
7.5 High
Exploitation
3% chance of attack within 30 days
Type
CWE-125Out-of-bounds Read
Timeline
Published22 May 2018
Updated31 Oct 2026
First seen29 Sep 2026
Sources
CVE-2018-11362 · NVD
Track software like this
Free during beta