CVE-2018-19627: High severity wireshark vulnerability

Published Nov 29, 2018
·
Updated

In Wireshark 2.6.0 to 2.6.4 and 2.4.0 to 2.4.10, the IxVeriWave file parser could crash. This was addressed in wiretap/vwr.c by adjusting a buffer boundary.

Affected Software

4 affected componentsFixes available
debian/wireshark
2.6.20-0+deb10u42.6.20-0+deb10u73.4.10-0+deb11u14.0.6-1~deb12u14.0.10-1
Wireshark Wireshark>=2.4.0<=2.4.10
Wireshark Wireshark>=2.6.0<=2.6.4
Debian Debian Linux=9.0

Event History

Nov 29, 2018
CVE Published
via MITRE·04:00 AM
Data Sourced
via MITRE·04:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2018-19627?

CVE-2018-19627 has a medium severity rating due to the potential for crashes in the IxVeriWave file parser.

2

How do I fix CVE-2018-19627?

To fix CVE-2018-19627, update Wireshark to version 2.6.20 or later, or 2.4.10 for affected versions.

3

Which versions of Wireshark are affected by CVE-2018-19627?

CVE-2018-19627 affects Wireshark versions 2.6.0 to 2.6.4 and 2.4.0 to 2.4.10.

4

Is there a workaround for CVE-2018-19627 if I can't update?

There is no known workaround for CVE-2018-19627; updating Wireshark is the best mitigation method.

5

What specific component of Wireshark does CVE-2018-19627 impact?

CVE-2018-19627 impacts the IxVeriWave file parser within Wireshark.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203