Loading vulnerability…
CVE-2015-0008 is an improper-authentication vulnerability in the UNC implementation used by Microsoft Windows Group Policy. Affected domain-joined Windows systems do not authenticate the server to the client before Group Policy receives and applies policy data from a domain controller. An attacker able to make crafted Group Policy data available through a UNC share, including by impersonating or redirecting a client to a spoofed domain controller on an attacker-controlled network, can cause execution of arbitrary code.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical remote code execution vulnerability in Microsoft Windows Group Policy affecting domain-joined systems when they connect to a domain controller on an attacker-controlled network.
A critical remote code execution design flaw in Windows Group Policy handling on domain-configured systems that can allow complete system compromise when connected to a malicious network.
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.