high
7.5
CWE
674
Advisory Published
Updated

CVE-2019-12295

First published: Thu May 23 2019(Updated: )

In Wireshark 3.0.0 to 3.0.1, 2.6.0 to 2.6.8, and 2.4.0 to 2.4.14, the dissection engine could crash. This was addressed in epan/packet.c by restricting the number of layers and consequently limiting recursion.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
debian/wireshark
3.4.10-0+deb11u1
3.4.16-0+deb11u1
4.0.11-1~deb12u1
4.4.0-1
4.4.1-1
Wireshark Wireshark>=2.4.0<=2.4.14
Wireshark Wireshark>=2.6.0<=2.6.8
Wireshark Wireshark>=3.0.0<=3.0.1
Debian=9.0
Ubuntu=16.04
Ubuntu=18.04
Ubuntu=19.04
F5 Access Policy Manager>=12.1.3.6<12.1.5.3
F5 Access Policy Manager>=13.1.1.2<13.1.3.5
F5 Access Policy Manager>=14.0.0.3<=14.0.1
F5 Access Policy Manager>=14.1.0<14.1.2.8
F5 Access Policy Manager>=15.0.0<=15.0.1
F5 Access Policy Manager=15.1.0
F5 BIG-IP Advanced Firewall Manager>=12.1.3.6<12.1.5.3
F5 BIG-IP Advanced Firewall Manager>=13.1.1.2<13.1.3.5
F5 BIG-IP Advanced Firewall Manager>=14.0.0.3<=14.0.1
F5 BIG-IP Advanced Firewall Manager>=14.1.0<14.1.2.8
F5 BIG-IP Advanced Firewall Manager>=15.0.0<=15.0.1
F5 BIG-IP Advanced Firewall Manager=15.1.0
F5 BIG-IP Analytics>=12.1.3.6<12.1.5.3
F5 BIG-IP Analytics>=13.1.1.2<13.1.3.5
F5 BIG-IP Analytics>=14.0.0.3<=14.0.1
F5 BIG-IP Analytics>=14.1.0<14.1.2.8
F5 BIG-IP Analytics>=15.0.0<=15.0.1
F5 BIG-IP Analytics=15.1.0
f5 big-ip application acceleration manager>=12.1.3.6<12.1.5.3
f5 big-ip application acceleration manager>=13.1.1.2<13.1.3.5
f5 big-ip application acceleration manager>=14.0.0.3<=14.0.1
f5 big-ip application acceleration manager>=14.1.0<14.1.2.8
f5 big-ip application acceleration manager>=15.0.0<=15.0.1
f5 big-ip application acceleration manager=15.1.0
F5 Application Security Manager>=12.1.3.6<12.1.5.3
F5 Application Security Manager>=13.1.1.2<13.1.3.5
F5 Application Security Manager>=14.0.0.3<=14.0.1
F5 Application Security Manager>=15.0.0<=15.0.1
F5 Application Security Manager=15.1.0
f5 big-ip domain name system>=12.1.3.6<12.1.5.3
f5 big-ip domain name system>=13.1.1.2<13.1.3.5
f5 big-ip domain name system>=14.0.0.3<=14.0.1
f5 big-ip domain name system>=14.1.0<14.1.2.8
f5 big-ip domain name system>=15.0.0<=15.0.1
f5 big-ip domain name system=15.1.0
F5 BIG-IP Edge Gateway>=12.1.3.6<12.1.5.3
F5 BIG-IP Edge Gateway>=13.1.1.2<13.1.3.5
F5 BIG-IP Edge Gateway>=14.0.0.3<=14.0.1
F5 BIG-IP Edge Gateway>=14.1.0<14.1.2
F5 BIG-IP Edge Gateway>=15.0.0<=15.0.1
F5 BIG-IP Edge Gateway=15.1.0
F5 BIG-IP fraud protection services>=12.1.3.6<12.1.5.3
F5 BIG-IP fraud protection services>=13.1.1.2<13.1.3.5
F5 BIG-IP fraud protection services>=14.0.0.3<=14.0.1
F5 BIG-IP fraud protection services>=14.1.0<14.1.2
F5 BIG-IP fraud protection services>=15.0.0<=15.0.1
F5 BIG-IP fraud protection services=15.1.0
F5 BIG-IP Global Traffic Manager>=12.1.3.6<12.1.5.3
F5 BIG-IP Global Traffic Manager>=13.1.1.2<13.1.3.5
F5 BIG-IP Global Traffic Manager>=14.0.0.3<=14.0.1
F5 BIG-IP Global Traffic Manager>=14.1.0<14.1.2.8
F5 BIG-IP Global Traffic Manager>=15.0.0<=15.0.1
F5 BIG-IP Global Traffic Manager=15.1.0
F5 BIG-IP>=12.1.3.6<12.1.5.3
F5 BIG-IP>=13.1.1.2<13.1.3.5
F5 BIG-IP>=14.0.0.3<=14.0.1
F5 BIG-IP>=14.1.0<14.1.2.8
F5 BIG-IP>=15.0.0<=15.0.1
F5 BIG-IP=15.1.0
F5 BIG-IP Local Traffic Manager>=12.1.3.6<12.1.5.3
F5 BIG-IP Local Traffic Manager>=13.1.1.2<13.1.3.5
F5 BIG-IP Local Traffic Manager>=14.0.0.3<=14.0.1
F5 BIG-IP Local Traffic Manager>=14.1.0<14.1.2.8
F5 BIG-IP Local Traffic Manager>=15.0.0<=15.0.1
F5 BIG-IP Local Traffic Manager=15.1.0
F5 BIG-IP Policy Enforcement Manager>=12.1.3.6<12.1.5.3
F5 BIG-IP Policy Enforcement Manager>=13.1.1.2<13.1.3.5
F5 BIG-IP Policy Enforcement Manager>=14.0.0.3<=14.0.1
F5 BIG-IP Policy Enforcement Manager>=14.1.0<14.1.2.8
F5 BIG-IP Policy Enforcement Manager>=15.0.0<=15.0.1
F5 BIG-IP Policy Enforcement Manager=15.1.0
F5 BIG-IP WebAccelerator>=12.1.3.6<12.1.5.3
F5 BIG-IP WebAccelerator>=13.1.1.2<13.1.3.5
F5 BIG-IP WebAccelerator>=14.0.0.3<=14.0.1
F5 BIG-IP WebAccelerator>=14.1.0<14.1.2.8
F5 BIG-IP WebAccelerator>=15.0.0<=15.0.1
F5 BIG-IP WebAccelerator=15.1.0

Remedy

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15778

Remedy

https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=7b6e197da4c497e229ed3ebf6952bae5c426a820

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2019-12295?

    CVE-2019-12295 is considered a high severity vulnerability due to its potential impact on the stability of the dissection engine in Wireshark.

  • How do I fix CVE-2019-12295?

    To fix CVE-2019-12295, update Wireshark to version 3.4.10, 3.4.16, 4.0.11, or a later version as specified in the affected software section.

  • Which versions of Wireshark are affected by CVE-2019-12295?

    CVE-2019-12295 affects Wireshark versions from 3.0.0 to 3.0.1, 2.6.0 to 2.6.8, and 2.4.0 to 2.4.14.

  • What kind of impact does CVE-2019-12295 have on users?

    CVE-2019-12295 can lead to crashes in Wireshark's dissection engine, potentially disrupting network analysis work.

  • Is there a workaround for CVE-2019-12295 if I cannot update Wireshark?

    There is no known workaround for CVE-2019-12295, so updating to a patched version is the recommended action.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203