Loading vulnerability…
The ReadDirectoryChangesW API function in Microsoft Windows 2000, XP, Server 2003, and Vista fails to enforce proper permission checks on child objects. This allows a local user with LIST (READ) access to a directory to use ReadDirectoryChangesW to monitor changes to files within that directory, even if they do not have LIST permissions on those files. As a result, the user can obtain sensitive metadata such as filenames and access times for files they should not be able to enumerate.
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 (1 hidden).
This repository contains a single C source file (spydir.c) and supporting documentation for a tool that monitors directory changes on Windows systems. The tool, when compiled and run as 'spydir.exe <directory_path>', uses the Windows API to watch for file and directory changes (additions, deletions, modifications, renames, etc.) within the specified directory and all its subdirectories. Notably, it is able to report changes even for files the user does not have access to, which is the core of the CVE-2007-0843 vulnerability. The README and in-code comments attribute the tool to Vladimir Dubrovin (3APA3A) and provide usage instructions. There are no hardcoded network endpoints or remote attack vectors; the exploit is purely local and targets the Windows file system. The repository is structured simply, with the main exploit logic contained in spydir.c, and is intended as a proof-of-concept for the referenced vulnerability.
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.
1 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.