CVE-2020-8657 affects EyesOfNetwork 5.3. The product installation uses the same default API key across installations, hardcoded as EONAPI_KEY in include/api_functions.php for API version 2.4.2. Because this secret is not unique per deployment and is effectively embedded in the application, an attacker can derive, calculate, or guess the administrator access token generated from or protected by that key. The core issue is the use of a hardcoded credential/secret shared by all installations, which undermines the trust model of the API authentication mechanism.
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 targeting EyesOfNetwork versions 5.1, 5.2, and 5.3 running on Linux. The exploit leverages multiple vulnerabilities (CVE-2020-8654, CVE-2020-8655, CVE-2020-8656, CVE-2020-8657, CVE-2020-9465) to achieve remote code execution as root. The main attack vector is via the web interface, exploiting command injection in the 'target' parameter of the AutoDiscovery feature. The module can bypass authentication using a hardcoded API key or SQL injection, depending on the version. It writes a malicious Nmap NSE script to disk and triggers it via a privileged Nmap execution, resulting in code execution as root. The module supports multiple payloads, including Meterpreter and reverse bash shells. The code is mature, weaponized, and part of the Metasploit framework, making it easy to use and customize. The only file present is a Ruby Metasploit module, and it contains all logic for exploitation, authentication bypass, and cleanup.
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.
3 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.