Loading vulnerability…
Actual Analyzer through 2014-08-29 is vulnerable to code execution due to improper handling of untrusted input, which is used as part of the data passed to an eval operation. This allows attackers to inject shell metacharacters, leading to arbitrary code execution on the server.
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 (actualanalyzer_ant_cookie_exec.rb) that exploits a remote command execution vulnerability (CVE-2014-5470) in ActualAnalyzer <= 2.81. The exploit targets the 'aa.php' endpoint, where an unauthenticated attacker can inject arbitrary shell commands via the 'ant' cookie. The module includes logic to check for the presence and version of ActualAnalyzer, discover analytics hosts through multiple endpoints (view.php, code.php, admin.php), and execute a customizable payload. The exploit is weaponized, allowing for arbitrary command execution on vulnerable servers. The code is written in Ruby and follows standard Metasploit module structure, with all logic contained in a single file.
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.