Loading vulnerability…
Symantec Web Gateway 5.0.x before 5.0.3 contains a vulnerability in its management GUI where application scripts are not properly access-restricted. This allows remote attackers to execute arbitrary code by injecting or including crafted data via the management interface.
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.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (2 hidden).
This repository contains a single Metasploit module targeting a command injection vulnerability (CVE-2012-0297) in Symantec Web Gateway 5.0.2.8. The exploit abuses the /spywall/ipchange.php endpoint, which is accessible without authentication, to execute arbitrary OS commands via the 'subnet' POST parameter. The module first checks for the presence of the vulnerable application by requesting /spywall/login.php and looking for a specific title in the response. If the target is confirmed, the exploit sends a crafted POST request to /spywall/ipchange.php, injecting the payload as a command. The exploit is operational and allows remote code execution as the web server user. The code is written in Ruby and is structured as a standard Metasploit module, making it easy to use within the Metasploit framework.
This repository contains a single Metasploit module targeting a local file inclusion (LFI) vulnerability in Symantec Web Gateway version 5.0.2.8 (CVE-2012-0297). The exploit works by injecting PHP code into the web server's access log via a crafted HTTP request, then leveraging a directory traversal flaw in the 'relfile' parameter of the '/spywall/releasenotes.php' endpoint to include and execute the injected code. The module checks for the presence of the vulnerable application, performs the injection, and then triggers code execution, typically resulting in a remote shell as the 'apache' user. The code is written in Ruby and is designed to be used within the Metasploit framework. The main endpoints involved are '/spywall/login.php' for detection and '/spywall/releasenotes.php?relfile=../../../../../usr/local/apache2/logs/access_log' for exploitation. The payload is customizable PHP code, allowing for arbitrary command execution on the target system.
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.