First published: Tue Apr 09 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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
debian/wireshark | 3.4.10-0+deb11u1 3.4.16-0+deb11u1 4.0.17-0+deb12u1 4.0.11-1~deb12u1 4.4.3-1 | |
Wireshark Wireshark | >=2.4.0<=2.4.13 | |
Wireshark Wireshark | >=2.6.0<=2.6.7 | |
Wireshark Wireshark | =3.0.0 | |
Fedora | =29 | |
Fedora | =30 | |
openSUSE | =15.0 | |
openSUSE | =15.1 | |
openSUSE | =42.3 | |
Debian | =9.0 | |
Ubuntu | =16.04 | |
Ubuntu | =18.04 | |
Ubuntu | =18.10 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-10896 has a medium severity level due to the potential for application crashes caused by the DOF dissector.
To fix CVE-2019-10896, upgrade to a patched version of Wireshark, specifically 3.4.10-0+deb11u1 or later.
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.
No formal workaround is available for CVE-2019-10896; updating Wireshark is the recommended action.
If CVE-2019-10896 is not addressed, the DOF dissector could crash, leading to potential data loss or disruption in network analysis.