Skip to main content
Mallory
← Back to News
endpoint-software-vulnerabilitywidely-deployed-product-advisory

Wireshark Kafka Dissector Crash Lets Malformed Traffic or PCAPs Terminate Analysis

Vulnerability Disclosure · 2 sources · Updated 3mo ago · First seen Jun 1, 2025

Wireshark Kafka Dissector Crash Lets Malformed Traffic or PCAPs Terminate Analysis

Wireshark disclosed CVE-2025-13499, a denial-of-service flaw in its Kafka dissector that can crash the application when it processes malformed network traffic or a specially crafted packet capture file. The issue affects Wireshark 4.6.0 and 4.4.0 through 4.4.10, and the project said no active exploits were known at disclosure. Users were advised to upgrade to Wireshark 4.6.1, 4.4.11, or later.

Project details show the bug was uncovered by an internal fuzzing job on the release-4.4 branch after tshark processed a crafted .pcap file and hit an assertion failure in epan/tvbuff.c. Developers traced the crash to Kafka Snappy decompression logic handling Xerial framing: when the length equaled 16, the code returned success without initializing the decompressed tvbuff pointer, leaving composite_tvb unset and causing the crash. Wireshark fixed the flaw in merge request !22037 and commit 49137f8c.

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.

4 events · Jun 1, 2025
  1. Reported Oct 25, 20251y ago

    Issue 20823 is noted as assigned CVE-2025-13499

    A later update on the Wireshark GitLab issue stated that the crash had been assigned CVE-2025-13499. This linked the previously tracked fuzzing issue to the published vulnerability identifier.

    Fuzz job crash: fuzz-2025-10-24-11832086494.pcap (#20823) · Issue · wireshark/wireshark
  2. Reported Oct 25, 20251y ago

    Wireshark fixes issue 20823 in merged code changes

    Wireshark resolved the Kafka dissector crash through merge request !22037 and commit 49137f8c, with related merge requests !22047 and !22048 carrying the same fix. The issue was marked done and closed in the project's GitLab tracker.

    Fuzz job crash: fuzz-2025-10-24-11832086494.pcap (#20823) · Issue · wireshark/wireshark
  3. Reported Oct 25, 20251y ago

    Wireshark internal fuzzing discovers Kafka dissector crash

    Wireshark's internal testing identified a crash in the Kafka dissector when tshark processed a crafted capture file on the release-4.4 branch. Developer analysis traced the fault to decompress_snappy returning success without initializing the decompressed tvbuff pointer in an Xerial framing edge case.

    Fuzz job crash: fuzz-2025-10-24-11832086494.pcap (#20823) · Issue · wireshark/wireshark
  4. Jun 1, 20251y ago

    Wireshark publishes advisory wnpa-sec-2025-06 for CVE-2025-13499

    Wireshark published security advisory wnpa-sec-2025-06 disclosing CVE-2025-13499, a Kafka dissector crash affecting version 4.6.0 and versions 4.4.0 through 4.4.10. The advisory said no exploits were known and directed users to upgrade to 4.6.1, 4.4.11, or later.

    Wireshark • Go Deep | Wireshark • wnpa-sec-2025-06 Kafka dissector 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

Organizations

1 linked
Wireshark Foundation
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.