CVE-2024-38213: copy2pwn
- Vendor
- Microsoft Corporation
CVE-2024-38213, also known as copy2pwn, is a Windows Mark of the Web security feature bypass affecting files copied from WebDAV shares through Windows Explorer. Clipboard copying and drag-and-drop can place files on the local system without the internet-origin marking required to trigger dependent security protections. An incomplete initial fix incorrectly treated a successful CoCreateInstance return value as failure in _InitializeZoneIdentifierInterfaces, skipping IInternetSecurityManager initialization. Consequently, _StampMotwOnDestFileIfNeeded could not perform the MapUrlToZone check and omitted the marking. The vulnerability has been exploited by DarkGate operators and Sandworm-linked UAC-0212 campaigns.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Files copied from untrusted WebDAV shares can receive excessive trust from Windows Explorer, SmartScreen, Microsoft Defender, and other controls that depend on Mark of the Web. This bypass suppresses applicable origin-based warnings or restrictions and facilitates malware delivery. It does not independently execute code or elevate privileges; subsequent execution of a malicious file can compromise the system in the user's security context.
Mitigation
If you can’t patch tonight, do this now.
Avoid copying or opening files from untrusted WebDAV shares, particularly files reached through unsolicited document links. Use endpoint protection capable of detecting malicious files and execution behavior independently of Mark of the Web. Do not treat the absence of an internet-origin warning as evidence that a file is trustworthy; drag-and-drop may display a warning while still failing to apply the marking.
Remediation
Patch, then assume compromise.
Install current Microsoft security updates containing the corrected fix for the affected Windows release. Do not assume the initial 2024 update fully resolved the issue: testing of systems updated through August 2024 found the bypass persisted on the examined versions other than Windows 11 and Windows Server 2022. Microsoft subsequently corrected the erroneous success check to branch on a failing HRESULT rather than zero. A logically equivalent 0patch micropatch was also developed for Windows 7, Windows Server 2008 R2, and several Windows 10 versions; exact applicable Microsoft update identifiers are not available here.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2024-38213 exploited in the wild?
- Yes. As of Oct 25, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Aug 13, 2024.
- Is there a public exploit for CVE-2024-38213?
- As of Oct 25, 2026, Mallory has found no public exploit for CVE-2024-38213.
- Is there a patch for CVE-2024-38213?
- Install current Microsoft security updates containing the corrected fix for the affected Windows release. Do not assume the initial 2024 update fully resolved the issue: testing of systems updated through August 2024 found the bypass persisted on the examined versions other than Windows 11 and Windows Server 2022.
- What products are affected by CVE-2024-38213?
- Microsoft Corporation Windows 10 1507, Microsoft Corporation Windows 10 1607, Microsoft Corporation Windows 10 1809, Microsoft Corporation Windows 10 21h2, Microsoft Corporation Windows 10 22h2, and 10 more.
- How severe is CVE-2024-38213?
- CVE-2024-38213 has a CVSS v3.1 score of 6.5 (Medium) and an EPSS score of 13.6% (97th percentile) as of Oct 25, 2026.
Recent activity
14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.