CVE-2011-1139: Medium severity wireshark vulnerability
Published Mar 3, 2011
·Updated
wiretap/pcapng.c in Wireshark 1.2.0 through 1.2.14 and 1.4.0 through 1.4.3 allows remote attackers to cause a denial of service (application crash) via a pcap-ng file that contains a large packet-length field.
Affected Software
19 affected components
Wireshark Wireshark=1.2.0
Wireshark Wireshark=1.2.1
Wireshark Wireshark=1.2.2
Wireshark Wireshark=1.2.3
Wireshark Wireshark=1.2.4
Wireshark Wireshark=1.2.5
Wireshark Wireshark=1.2.6
Wireshark Wireshark=1.2.7
Wireshark Wireshark=1.2.8
Wireshark Wireshark=1.2.9
Wireshark Wireshark=1.2.10
Wireshark Wireshark=1.2.11
Wireshark Wireshark=1.2.12
Wireshark Wireshark=1.2.13
Wireshark Wireshark=1.2.14
Wireshark Wireshark=1.4.0
Wireshark Wireshark=1.4.1
Wireshark Wireshark=1.4.2
Wireshark Wireshark=1.4.3
Remediation
Patch Available
Patch Available
Patch Available
Event History
Mar 3, 2011
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Frequently Asked Questions
1
What is the severity of CVE-2011-1139?
CVE-2011-1139 is classified as a denial of service vulnerability that can cause an application crash.
2
How do I fix CVE-2011-1139?
To fix CVE-2011-1139, update Wireshark to version 1.2.15 or later, or to version 1.4.4 or later.
3
Which versions of Wireshark are affected by CVE-2011-1139?
Wireshark versions 1.2.0 through 1.2.14 and 1.4.0 through 1.4.3 are affected by CVE-2011-1139.
4
What types of attacks can exploit CVE-2011-1139?
CVE-2011-1139 can be exploited by remote attackers through specially crafted pcap-ng files.
5
Is there a known exploit for CVE-2011-1139?
Yes, there are reports of remote attackers using crafted pcap-ng files to exploit CVE-2011-1139.