CVE-2012-3826: Low severity wireshark vulnerability
Published Jun 30, 2012
·Updated
Multiple integer underflows in Wireshark 1.4.x before 1.4.13 and 1.6.x before 1.6.8 allow remote attackers to cause a denial of service (loop) via vectors related to the R3 dissector, a different vulnerability than CVE-2012-2392.
Affected Software
22 affected components
Wireshark Wireshark=1.4.0
Wireshark Wireshark=1.4.1
Wireshark Wireshark=1.4.2
Wireshark Wireshark=1.4.3
Wireshark Wireshark=1.4.4
Wireshark Wireshark=1.4.5
Wireshark Wireshark=1.4.6
Wireshark Wireshark=1.4.7
Wireshark Wireshark=1.4.8
Wireshark Wireshark=1.4.9
Wireshark Wireshark=1.4.10
Wireshark Wireshark=1.4.11
Wireshark Wireshark=1.4.12
Wireshark Wireshark=1.4.13
Wireshark Wireshark=1.6.0
Wireshark Wireshark=1.6.1
Wireshark Wireshark=1.6.2
Wireshark Wireshark=1.6.3
Wireshark Wireshark=1.6.4
Wireshark Wireshark=1.6.5
Wireshark Wireshark=1.6.6
Wireshark Wireshark=1.6.7
Event History
Jun 30, 2012
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description
Frequently Asked Questions
1
What is the severity of CVE-2012-3826?
CVE-2012-3826 is classified as a moderate severity vulnerability due to its ability to cause denial of service.
2
How do I fix CVE-2012-3826?
To fix CVE-2012-3826, you should update Wireshark to version 1.4.13 or 1.6.8 or later.
3
What versions of Wireshark are affected by CVE-2012-3826?
CVE-2012-3826 affects Wireshark versions 1.4.0 to 1.4.12 and 1.6.0 to 1.6.7.
4
What type of attacks can CVE-2012-3826 facilitate?
CVE-2012-3826 can facilitate denial of service attacks through remote exploitation.
5
Is CVE-2012-3826 a known issue in Wireshark?
Yes, CVE-2012-3826 is a known issue in Wireshark that has been addressed in subsequent software updates.