CVE-2019-10896: High severity wireshark vulnerability
Published Apr 9, 2019
·Updated
In Wireshark 2.4.0 to 2.4.13, 2.6.0 to 2.6.7, and 3.0.0, the DOF dissector could crash. This was addressed in epan/dissectors/packet-dof.c by properly handling generated IID and OID bytes.
Affected Software
13 affected componentsFixes available
debian/wireshark
3.4.10-0+deb11u13.4.16-0+deb11u14.0.17-0+deb12u14.0.11-1~deb12u14.4.3-1
Wireshark Wireshark>=2.4.0<=2.4.13
Wireshark Wireshark>=2.6.0<=2.6.7
Wireshark Wireshark=3.0.0
Fedoraproject Fedora=29
Fedoraproject Fedora=30
openSUSE Leap=15.0
openSUSE Leap=15.1
openSUSE Leap=42.3
Debian Debian Linux=9.0
Canonical Ubuntu Linux=16.04
Canonical Ubuntu Linux=18.04
Canonical Ubuntu Linux=18.10
Remediation
Patch Available
Event History
Apr 9, 2019
CVE Published
via MITRE·03:50 AM
Data Sourced
via MITRE·03:50 AM
Description
Jan 11, 2024
Data Sourced
via Launchpad·11:12 PM
Description
Sep 13, 2024
Data Sourced
via Ubuntu·09:50 PM
RemedyDescriptionSeverityAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2019-10896?
CVE-2019-10896 has a medium severity level due to the potential for application crashes caused by the DOF dissector.
2
How do I fix CVE-2019-10896?
To fix CVE-2019-10896, upgrade to a patched version of Wireshark, specifically 3.4.10-0+deb11u1 or later.
3
Which versions of Wireshark are affected by CVE-2019-10896?
CVE-2019-10896 affects Wireshark versions from 2.4.0 to 2.4.13, 2.6.0 to 2.6.7, and the 3.0.0 version.
4
Is there a workaround for CVE-2019-10896?
No formal workaround is available for CVE-2019-10896; updating Wireshark is the recommended action.
5
What could happen if I don't address CVE-2019-10896?
If CVE-2019-10896 is not addressed, the DOF dissector could crash, leading to potential data loss or disruption in network analysis.