CVE-2010-2287: Buffer Overflow
Published Jun 15, 2010
·Updated
Buffer overflow in the SigComp Universal Decompressor Virtual Machine dissector in Wireshark 0.10.8 through 1.0.13 and 1.2.0 through 1.2.8 has unknown impact and remote attack vectors.
Affected Software
39 affected components
Wireshark Wireshark=0.99.8
Wireshark Wireshark=1.0.13
Wireshark Wireshark=0.99.3
Wireshark Wireshark=0.99.0
Wireshark Wireshark=1.0.9
Wireshark Wireshark=1.0.1
Wireshark Wireshark=0.10.14
Wireshark Wireshark=0.10.9
Wireshark Wireshark=0.10.8
Wireshark Wireshark=0.99.6
Wireshark Wireshark=1.0.2
Wireshark Wireshark=0.99.2
Wireshark Wireshark=0.99.1
Wireshark Wireshark=1.0.4
Wireshark Wireshark=1.0.3
Wireshark Wireshark=1.0.6
Wireshark Wireshark=1.0.10
Wireshark Wireshark=0.10.13
Wireshark Wireshark=1.0.12
Wireshark Wireshark=0.10.12
Wireshark Wireshark=0.10.10
Wireshark Wireshark=1.0.8
Wireshark Wireshark=1.0.5
Wireshark Wireshark=0.99.5
Wireshark Wireshark=0.10.11
Wireshark Wireshark=0.99.4
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-2287?
The severity of CVE-2010-2287 is currently unknown but involves a buffer overflow vulnerability that could lead to potential remote exploitation.
2
How do I fix CVE-2010-2287?
To fix CVE-2010-2287, upgrade to a later version of Wireshark that addresses this buffer overflow vulnerability.
3
Which versions of Wireshark are affected by CVE-2010-2287?
CVE-2010-2287 affects Wireshark versions from 0.10.8 to 1.2.8, including several specific versions mentioned.
4
What are the implications of CVE-2010-2287?
CVE-2010-2287 may lead to remote code execution or application crashes due to a buffer overflow.
5
Is there any workaround for CVE-2010-2287?
There is no specific workaround for CVE-2010-2287, so updating to a fixed version is recommended.