Loading vulnerability…
CVE-2018-5410 is a stack-based buffer overflow in the Dokany/Dokan kernel-mode file system driver, specifically in dokan1.sys, affecting versions from 1.0.0.5000 through 1.2.0.1000. The flaw is reachable by opening a handle to the driver device (for example, "dokan_1") and sending crafted input to IOCTL 0x00222010. The vulnerable code is in notification.c, where the szMountPoint->Length field is not properly validated before an RtlCopyMemory operation copies attacker-controlled data into the fixed-size dokanControl.MountPoint stack buffer. Supplying an oversized input buffer, reported as larger than 776 bytes and with approximately 896 bytes sufficient to overwrite a stack exception handler, corrupts stack memory and the stack cookie, leading to kernel instability. The vulnerable code path was introduced in Dokany version 1.0.0.5000. The issue also affected downstream products using Dokany-derived drivers, including certain versions of Google Drive File Stream that incorporated a modified variant of the 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.
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.