Skip to main content
Mallory
← Back to News
endpoint-software-vulnerabilitywidely-deployed-product-advisoryproof-of-concept-release

Wireshark CVE-2025-5601 Lets Malformed Packets Crash the Dissection Engine

Vulnerability Disclosure · 2 sources · Updated 2mo ago · First seen Apr 26, 2025

Wireshark CVE-2025-5601 Lets Malformed Packets Crash the Dissection Engine

Wireshark disclosed CVE-2025-5601, a denial-of-service flaw in its dissection engine’s column utility handling. A remote attacker could inject a malformed packet onto a monitored network, or trick an analyst into opening a crafted capture file, to crash Wireshark or TShark. The affected releases are Wireshark 4.4.0–4.4.6 and 4.2.0–4.2.11; Wireshark reported no known exploitation and said the issue was identified through internal testing.

Fuzzing of a crafted PCAP uncovered an out-of-bounds heap write in CLNP dissection paths that invoked column-handling functions, corrupting heap metadata and causing Valgrind to abort. The remediation constrains column-fence handling during prepending so it cannot exceed the column size. Wireshark’s advisory identifies 4.2.12 and 4.4.7 as fixed releases, while the associated development issue was subsequently retargeted to 4.4.8, so organizations should deploy the latest supported Wireshark maintenance release.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

3 events · Apr 25, 2025 – Apr 26, 2025
  1. Apr 26, 20252y ago

    Wireshark closes and fixes the TShark crash issue

    Wireshark closed issue #20509 after fixes were merged, including a change preventing column fences from exceeding column size during prepending. John Thacker closed the issue with commit 53213086.

    Fuzz job crash: fuzz-2025-04-25-7554.pcap (#20509) · Issue · wireshark/wireshark
  2. Apr 25, 20252y ago

    Wireshark fuzzing detects CLNP column-handling heap write

    Wireshark's automated Valgrind Menagerie fuzz job found out-of-bounds heap writes while TShark processed a crafted PCAP on the release-4.4 branch. The writes originated in CLNP dissection paths invoking column utility functions and corrupted heap metadata.

    Fuzz job crash: fuzz-2025-04-25-7554.pcap (#20509) · Issue · wireshark/wireshark
  3. Reported Feb 1, 20252y ago

    Wireshark discloses CVE-2025-5601 and releases fixes

    Wireshark published advisory wnpa-sec-2025-02 for CVE-2025-5601, a dissection-engine crash caused by a column utility module bug affecting versions 4.4.0–4.4.6 and 4.2.0–4.2.11. Wireshark identified the issue through internal testing, stated it was unaware of exploitation, and listed versions 4.4.7 and 4.2.12 as fixes.

    Wireshark • Go Deep | Wireshark • wnpa-sec-2025-02 Dissection engine crash
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Affected products

1 linked
Wireshark
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.