Loading vulnerability…
A stack-based buffer overflow exists in the mk_request_header_process function in mk_request.c in Monkey HTTP Daemon (monkeyd) before version 1.2.1. Remote attackers can exploit this vulnerability by sending specially crafted HTTP headers, leading to a denial of service (crash) and potentially arbitrary code execution.
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.
This repository contains a single Metasploit auxiliary module targeting Monkey HTTPD (versions <= 1.2.0) for a denial of service (DoS) attack. The module, written in Ruby, is located at 'modules/auxiliary/dos/http/monkey_headers.rb'. It exploits CVE-2013-3843 by sending a specially crafted HTTP request with malformed headers to the target server (default port 2001). If successful, the server crashes due to a segmentation fault, resulting in a denial of service. The module includes logic to check if the server is still alive after the attack. The exploit is a proof-of-concept and does not provide post-exploitation capabilities. No hardcoded IP addresses or URLs are present; the target is specified by the user. The code is structured as a standard Metasploit module, with clear separation of initialization, attack, and verification logic.
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.