Loading vulnerability…
A buffer overflow vulnerability exists in Flexense VX Search Enterprise 10.1.12. The vulnerability is triggered by sending an empty POST request to a long URI that begins with a /../ substring. This can cause a buffer overflow condition, potentially allowing remote attackers to execute arbitrary code on the affected system.
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).
Repository contains a single Python proof-of-exploit script (CVE-2017-15220.py) and a short README. The exploit targets Flexense VX Search Enterprise 10.1.12 (Windows, tested on Win7 x86 SP1) and achieves unauthenticated remote code execution by sending a crafted HTTP POST request to the server on TCP/80. The request line is built as `POST /../%s HTTP/1.1` where `%s` is a 5000-byte buffer designed to trigger a stack-based overflow with SEH overwrite. Exploit structure/capabilities: - Builds a 5000-byte payload with: - Padding up to the SEH record offset (dist_seh=2492) - nSEH short jump ("\xEB\x06AA") - SEH handler overwrite with a hardcoded address (0x1011369e) - NOP sled + egghunter - Egg tag `w00tw00t` followed by embedded x86 shellcode - Shellcode is noted as generated by msfvenom: `windows/shell_bind_tcp` on port 4444, encoded with `x86/alpha_mixed`. - Sends the malicious HTTP request to a hardcoded target IP `10.10.10.10` on port 80 and closes the connection. Overall purpose: a working remote buffer overflow exploit (not merely detection) intended to pop a bind shell on the victim, with hardcoded target parameters and a fixed SEH address that may require adjustment for different environments/builds.
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.