CVE-2024-38213
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWindows Mark of the Web Security Feature Bypass Vulnerability
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a security feature bypass vulnerability in Windows Mark of the Web (MOTW), a protective mechanism that applies Zone.Identifier metadata to files downloaded from the internet or originating from untrusted sources. The bypass allows attackers to circumvent this protection, potentially enabling malicious files to execute without the expected security restrictions or user warnings that MOTW typically enforces.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 10.0.10240.20680< 10.0.14393.7070< 10.0.17763.5936< 10.0.19044.4529< 10.0.19045.4529< 10.0.22000.3019< 10.0.22621.3737< 10.0.22631.3737CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check your Windows build versionRun `winver` or `systeminfo | findstr /B /C:"OS Version"` and note the build numberAffected if The build number is below 10240.20680 (Win10 1507), 14393.7070 (Win10 1607), 17763.5936 (Win10 1809), 19044.4529 (Win10 21h2), 19045.4529 (Win10 22h2), 22000.3019 (Win11 21h2), 22621.3737 (Win11 22h2), or 22631.3737 (Win11 23h2)
-
Verify the full Windows version nameRun `winver` and confirm the exact release (such as Windows 10 22h2 or Windows 11 23h2)Affected if The release matches an affected version but the build is below the corresponding threshold in step 1
-
Test if MotW is being applied to downloaded filesDownload a file from the internet, then right-click the file, select Properties, and look for a Security notice under General indicating the file was downloaded from the internetAffected if The Security notice is missing or the Zone.Identifier alternate data stream (viewable via `dir /r` or `Get-Item -Stream Zone.Identifier`) is not present on files downloaded from untrusted sources
-
Check NTFS file system usageRun `fsutil fsinfo volumeinfo C:` and confirm NTFS is the file systemAffected if The volume is not formatted as NTFS, as MotW protection relies on NTFS alternate data streams
You are affected if you are running any Windows 10 or Windows 11 version listed as vulnerable and the Mark of the Web feature is not properly tagging or warning about files from untrusted sources.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped10.0.10240.2068010.0.14393.707010.0.17763.5936
Apply the Microsoft security updates for CVE-2024-38213 once released, as this addresses a bypass of a core Windows security feature designed to protect users from untrusted files.
June 2024 Security Updates (KB5039212 for Windows 10, KB5039219 for Windows 11) or later - specific to your Windows version and build
- Identify the current Windows version and build by running 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
- Determine if the current build is below the fixed version for your Windows release
- Open Settings > Update & Security > Windows Update and check for updates
- Install the June 2024 Security Updates (or later) from Microsoft Update
- Alternatively, download and install the specific cumulative update for your Windows version from the Microsoft Update Catalog
- Restart the system after installing the update
- Verify the installed build matches or exceeds the fixed version by running 'winver'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-38213 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-38213 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data