Loading vulnerability…
A buffer overflow vulnerability exists in the blocking_request.cgi function of the httpd module in ASUS RT-AX86U router firmware versions below 9.0.0.4_386. An attacker can exploit this vulnerability by sending specially crafted data to the affected CGI endpoint, leading to a buffer overflow condition and potential arbitrary code execution on the device.
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 proof-of-concept (PoC) exploit for CVE-2020-36109, a buffer overflow vulnerability in the httpd service of certain ASUS routers (including RT-AX86U, ROG Rapture GT-AC5300, and GT-AX11000) running firmware below 9.0.0.4_386. The exploit is implemented in Python (poc.py) and sends a specially crafted POST request to the /blocking_request.cgi endpoint, attempting to overflow a buffer and cause a Denial of Service (DoS) on the router's web interface. The README.md provides detailed vulnerability and usage information, including prerequisites for successful exploitation. The exploit does not achieve remote code execution due to stack canaries and buffer placement, but reliably causes a DoS if the target is vulnerable. The only code file is poc.py, which is the main entry point and contains all exploit logic. No hardcoded IPs or domains are present; the target is specified via command-line arguments.
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.