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

CVE-2018-7331: Wireshark may freeze when processing certain data

CVE-2018-7331 · published 8 years ago

Summary

Wireshark versions 2.2.0 through 2.2.12 and 2.4.0 through 2.4.4 contain a coding error that can cause the program to get stuck in a loop when it receives specially crafted network information. This can make the application stop responding, affecting any user who opens a capture containing the problem data. Updating to a newer Wireshark release or applying the provided patches resolves the issue.

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

Vendor	Product	Affected versions
wireshark	wireshark	>= 2.2.0, <= 2.2.12 >= 2.4.0, <= 2.4.4 `cpe:2.3:a:wireshark:wireshark::::::::`
debian	debian_linux	8.0 `cpe:2.3:o:debian:debian_linux:8.0:::::::*`

Original advisory text

In Wireshark 2.4.0 to 2.4.4 and 2.2.0 to 2.2.12, epan/dissectors/packet-ber.c had an infinite loop that was addressed by validating a length.

References

http://www.securityfocus.com/bid/103158 Third Party Advisory VDB Entry
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14444 Issue Tracking Vendor Advisory
https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=157712b2...
https://lists.debian.org/debian-lts-announce/2019/01/msg00010.html Mailing List Third Party Advisory
https://www.wireshark.org/security/wnpa-sec-2018-06.html Vendor Advisory

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

2% chance of attack within 30 days

Type

CWE-835Loop with Unreachable Exit Condition ('Infinite Loop')

Timeline

Published23 Feb 2018

Updated29 Oct 2026

First seen29 Sep 2026

Sources

CVE-2018-7331 · NVD

Track software like this

Free during beta