Loading vulnerability…
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Small standalone Python exploit repository for a claimed unauthenticated SSRF in Xiaomi Mi Router 4A Gigabit Edition firmware 3.0.24. The repository contains one executable script (xiaomi_ssrf_exploit.py), a README with vulnerability description and usage examples, plus license and gitignore files. The exploit is not part of a larger framework. The script targets the router web endpoint /cgi-bin/luci/api/xqsystem/login and abuses Host header injection by sending an HTTP GET request to the router while setting the Host header to an attacker-chosen IP:port. According to the code and README, this causes the router to initiate an outbound TCP connection to the supplied destination, enabling SSRF. Main capabilities: - Vulnerability check mode: starts a local TCP listener on port 44444, discovers the operator's local IP, sends the SSRF trigger, and confirms exploitation if the router connects back. - Callback demonstration mode: sends a single SSRF trigger to force the router to connect to an operator-controlled listener. - Internal port scanning mode: iterates over supplied ports and infers open vs closed ports on an internal target using response timing and timeout behavior. Code structure is straightforward: a XiaomiSSRFExploit class implements send_ssrf(), callback_exploit(), port_scan(), and check_vulnerability(); main() parses CLI arguments and dispatches to the selected mode. The exploit uses the Python requests library for the trigger request and socket/threading primitives for local callback verification. This is an operational PoC rather than a full post-exploitation tool: it provides a usable SSRF primitive and basic scanning workflow, but no advanced payload delivery beyond arbitrary outbound TCP connection triggering.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.