A vulnerability exists in the SPBBCDrv.sys driver used by Symantec Norton Personal Firewall 2006 (versions 9.1.0.33 and 9.1.1.7) and Norton Internet Security 2008 (15.0.0.60), as well as possibly other versions back to 2006. The driver fails to properly validate arguments before passing them to hooked SSDT function handlers, specifically for NtCreateMutant and NtOpenEvent. This allows local attackers to supply crafted arguments, potentially leading to a denial of service (system crash) or arbitrary code execution in kernel context.
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.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.