Loading vulnerability…
Symantec Messaging Gateway (SMG) versions prior to 10.0 contain a default password for an unspecified account. This default credential can be used by remote attackers to gain privileged access to the system via SSH, bypassing normal authentication controls.
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/linux/ssh/symantec_smg_ssh.rb) that exploits a default credential vulnerability (CVE-2012-3579) in Symantec Messaging Gateway 9.5. The exploit targets the SSH service (port 22) on the appliance, attempting to authenticate using the default credentials 'support'/'symantec'. Upon successful authentication, it provides the attacker with an interactive command shell with privileged access. The module is written in Ruby and leverages Metasploit's SSH libraries. No hardcoded IPs or domains are present; the attacker specifies the target. The exploit is operational and requires the target to be accessible over the network with default credentials enabled.
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.