CVE-2011-0024: Buffer Overflow

Published Jan 21, 2011
·
Updated

Heap-based buffer overflow in wiretap/pcapng.c in Wireshark before 1.2 allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted capture file.

Other sources

Marc Schoenefeld found a heap-based buffer overflow in Wireshark, when reading certain capture files.

A remote attacker could use this flaw to cause wireshark executable to crash or, potentially, execute arbitrary code with the privileges of the user running wireshark, if the local user opened a specially-crafted capture file.

This only affects wireshark < 1.2

Red Hat

Affected Software

24 affected components
Wireshark Wireshark<=1.0.16
Wireshark Wireshark=0.99.2
Wireshark Wireshark=0.99.3
Wireshark Wireshark=0.99.4
Wireshark Wireshark=0.99.5
Wireshark Wireshark=0.99.6
Wireshark Wireshark=0.99.7
Wireshark Wireshark=0.99.8
Wireshark Wireshark=1.0.0
Wireshark Wireshark=1.0.1
Wireshark Wireshark=1.0.2
Wireshark Wireshark=1.0.3
Wireshark Wireshark=1.0.4
Wireshark Wireshark=1.0.5
Wireshark Wireshark=1.0.6
Wireshark Wireshark=1.0.7
Wireshark Wireshark=1.0.8
Wireshark Wireshark=1.0.9
Wireshark Wireshark=1.0.10
Wireshark Wireshark=1.0.11
Wireshark Wireshark=1.0.12
Wireshark Wireshark=1.0.13
Wireshark Wireshark=1.0.14
Wireshark Wireshark=1.0.15

Event History

Jan 21, 2011
Data Sourced
via Red Hat·09:25 AM
DescriptionSeverityAffected Software
Mar 28, 2011
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2011-0024?

CVE-2011-0024 has been classified as a critical vulnerability due to its potential to cause denial of service and possibly execute arbitrary code.

2

How do I fix CVE-2011-0024?

To fix CVE-2011-0024, update Wireshark to the latest version that addresses this vulnerability.

3

Which versions of Wireshark are affected by CVE-2011-0024?

CVE-2011-0024 affects multiple versions of Wireshark, including versions up to 1.0.16 and specific earlier versions.

4

What could happen if CVE-2011-0024 is exploited?

If exploited, CVE-2011-0024 could lead to application crashes and potentially allow attackers to execute arbitrary code.

5

Is there a workaround for CVE-2011-0024?

There is no known workaround for CVE-2011-0024; the recommended action is to update to a patched version of 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