Loading vulnerability…
A stack-based buffer overflow vulnerability exists in Symantec Antivirus 10.1 and Client Security 3.1. The flaw allows remote attackers to execute arbitrary code by exploiting an overflow condition via unspecified attack vectors. The vulnerability is due to improper bounds checking on user-supplied input, leading to overwriting of stack memory.
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 exploit module targeting a stack buffer overflow vulnerability (CVE-2006-2630) in Symantec Client Security 3.0.x, specifically tested against version 3.0.2 build 10.0.2.2000 on Windows. The exploit connects to the Symantec Remote Management service on TCP port 2967, crafts a specially designed buffer to trigger the overflow, and delivers a customizable Metasploit payload (such as a shell or Meterpreter). The module is written in Ruby and follows the standard Metasploit exploit structure, including target selection, payload configuration, and network communication. The exploit provides remote code execution with the privileges of the Symantec service process. No hardcoded IP addresses or URLs are present; the only fingerprintable endpoint is the TCP port 2967 used by the vulnerable service.
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.