CVE-2010-2283: Null Pointer Dereference
Published Jun 15, 2010
·Updated
The SMB dissector in Wireshark 0.99.6 through 1.0.13, and 1.2.0 through 1.2.8 allows remote attackers to cause a denial of service (NULL pointer dereference) via unknown vectors.
Affected Software
26 affected components
Wireshark Wireshark=0.99.8
Wireshark Wireshark=1.0.13
Wireshark Wireshark=1.0.9
Wireshark Wireshark=1.0.1
Wireshark Wireshark=0.99.6
Wireshark Wireshark=1.0.2
Wireshark Wireshark=1.0.4
Wireshark Wireshark=1.0.3
Wireshark Wireshark=1.0.6
Wireshark Wireshark=1.0.10
Wireshark Wireshark=1.0.12
Wireshark Wireshark=1.0.8
Wireshark Wireshark=1.0.5
Wireshark Wireshark=1.0.0
Wireshark Wireshark=1.0.11
Wireshark Wireshark=0.99.7
Wireshark Wireshark=1.0.7
Wireshark Wireshark=1.2.7
Wireshark Wireshark=1.2.6
Wireshark Wireshark=1.2.8
Wireshark Wireshark=1.2.0
Wireshark Wireshark=1.2.3
Wireshark Wireshark=1.2.5
Wireshark Wireshark=1.2.1
Wireshark Wireshark=1.2.4
Wireshark Wireshark=1.2.2
Remediation
Patch Available
Event History
Jun 15, 2010
CVE Published
via MITRE·01:00 AM
Data Sourced
via MITRE·01:00 AM
Description
Frequently Asked Questions
1
What is the severity of CVE-2010-2283?
CVE-2010-2283 is classified as a denial of service vulnerability that can impact affected versions of Wireshark.
2
How do I fix CVE-2010-2283?
To mitigate CVE-2010-2283, upgrade to a version of Wireshark that is not vulnerable, specifically versions newer than 1.2.8.
3
Which versions are affected by CVE-2010-2283?
Affected versions by CVE-2010-2283 include Wireshark 0.99.6 through 1.0.13 and 1.2.0 through 1.2.8.
4
Can CVE-2010-2283 be exploited remotely?
Yes, CVE-2010-2283 can be exploited remotely via unknown vectors leading to a denial of service.
5
What type of impact does CVE-2010-2283 have on Wireshark?
The impact of CVE-2010-2283 on Wireshark results in a NULL pointer dereference, causing the application to crash.