Loading vulnerability…
A remote code execution vulnerability in the Windows Lightweight Directory Access Protocol (LDAP) client can be exploited by an unauthenticated attacker that wins a race condition and sends specially crafted LDAP requests to a vulnerable server. Successful exploitation results in arbitrary code execution in the context of the SYSTEM account. The available information identifies the issue as an LDAP client flaw involving a race condition, but does not provide function-level implementation details.
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 public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this 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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A remote code execution vulnerability in the LDAP client that allows unauthenticated attackers to execute code as SYSTEM by exploiting a race condition.
Remote code execution vulnerability in Windows LDAP involving use-after-free or improper synchronization when accessing shared resources; exploitable by unauthenticated attackers via crafted requests and requiring a race condition win.
A remote code execution vulnerability affecting an LDAP client component.
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.