The dissect_capwap_data function in epan/dissectors/packet-capwap.c in the CAPWAP dissector of Wireshark 1.6.x before 1.6.16 and 1.8.x before 1.8.8 improperly uses a -1 data value to indicate an error condition. This flaw allows remote attackers to crash the application by sending a specially crafted CAPWAP packet, resulting in a denial of service.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a single Metasploit auxiliary module (modules/auxiliary/dos/wireshark/capwap.rb) that exploits a denial-of-service vulnerability (CVE-2013-4074) in the CAPWAP dissector of Wireshark and TShark (versions 1.8.0-1.8.7 and 1.6.0-1.6.15). The exploit works by sending a specifically crafted malformed UDP packet to port 5247, which is the standard CAPWAP port. When Wireshark or TShark attempts to dissect this packet, the process crashes, resulting in a denial of service. The module is written in Ruby and is designed to be run within the Metasploit framework. The only network endpoint involved is UDP port 5247, and there are no hardcoded IP addresses or domain names. The exploit is operational and can be used to crash vulnerable Wireshark/TShark instances that are monitoring CAPWAP traffic.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.