CVE-2017-13708 is a buffer overflow vulnerability in the web server service of VX Search Enterprise 10.0.14. The issue can be triggered remotely by sending a crafted HTTP GET request to the affected service. Due to improper bounds checking while processing attacker-controlled request data, a remote attacker can overflow a buffer and potentially gain control of program execution, resulting in arbitrary code execution in the context of the vulnerable service.
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 module (modules/exploits/windows/http/vxsrchs_bof.rb) that exploits a stack-based buffer overflow vulnerability (CVE-2017-13708) in the web interface of VX Search Enterprise v9.5.12. The exploit targets the HTTP GET request handler of the built-in web server, overflowing the request path buffer to achieve arbitrary code execution. The module uses an egghunter to locate the payload in memory and supports customizable Metasploit payloads up to 500 bytes, avoiding specific bad characters. The exploit has been tested on Windows 7 SP1 x86. The module includes a version check routine and delivers the exploit via a crafted HTTP GET request. The only endpoints involved are the root path (for version checking) and the vulnerable path (for exploitation). The code is written in Ruby and is structured according to Metasploit conventions.
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.
2 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.