CVE-2019-10896: High severity Wireshark Wireshark vulnerability
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
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/wiresharkto a version that resolves this vulnerability.Fixed in 3.4.10-0+deb11u1Fixed in 3.4.16-0+deb11u1Fixed in 4.0.17-0+deb12u1Fixed in 4.0.11-1~deb12u1Fixed in 4.4.3-1 - Upgrade
Upgrade
alpine/wiresharkto a version that resolves this vulnerability.Fixed in 2.6.8-r0
Event History
Frequently Asked Questions
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.
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.
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.
Is there a workaround for CVE-2019-10896?
No formal workaround is available for CVE-2019-10896; updating Wireshark is the recommended action.
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.