Loading vulnerability…
A stack-based buffer overflow exists in the DECT dissector implementation in epan/dissectors/packet-dect.c in Wireshark versions 1.4.x prior to 1.4.5. The vulnerability can be triggered by a specially crafted .pcap file containing malformed DECT protocol data, leading to a buffer overflow on the stack.
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.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (2 hidden).
This repository contains a single Metasploit module (modules/exploits/windows/misc/wireshark_packet_dect.rb) that exploits a stack buffer overflow vulnerability (CVE-2011-1591) in Wireshark versions up to 1.4.4, specifically in the DECT packet parser (packet-dect.c). The exploit works by sending a specially crafted network packet to an interface being monitored by Wireshark, causing a buffer overflow and allowing arbitrary code execution. The module includes ROP chains to bypass DEP and ASLR on Windows, and supports customizable Metasploit payloads up to 936 bytes. The exploit can be configured to send the malicious packet repeatedly or just once, and is operational against any Windows system running a vulnerable version of Wireshark actively capturing packets. The only fingerprintable endpoint is the vulnerable file (packet-dect.c) in the target application. The code is written in Ruby and is structured as a standard Metasploit exploit module.
This repository contains a single Metasploit module (wireshark_packet_dect.rb) that exploits a stack buffer overflow vulnerability (CVE-2011-1591) in Wireshark versions 1.4.4 and earlier on Windows. The exploit works by generating a malicious .pcap file (default name: passwords.pcap) containing a specially crafted packet that triggers the overflow when opened in Wireshark. The module uses ROP chains to bypass DEP and ASLR protections, allowing arbitrary code execution with the privileges of the user running Wireshark. The payload is customizable and can be any Metasploit-compatible shellcode up to 936 bytes. The attack vector is local, requiring the victim to open the malicious file. The repository is structured as a single Ruby file compatible with the Metasploit framework, and does not contain any network endpoints or external IPs/domains. Its primary purpose is to demonstrate and exploit the vulnerability for penetration testing and research.
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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.