dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 5 Mar 2024.
Windows 10 1507Operating system · Microsoft

CVE-2024-21351

HIGH · 7.6 CVSS v3.1 Published 2024-02-13
Fix available
A fix is available. Upgrade to 10.0.10240.20469 / 10.0.14393.6709 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable No privileges Patch available

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 · unedited
Windows SmartScreen 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 confidence

This is a security feature bypass vulnerability in Windows SmartScreen, which is Microsoft's reputation-based security feature that warns users about potentially malicious files and websites. The vulnerability allows an attacker to circumvent SmartScreen protections, potentially enabling the delivery of malicious content without triggering expected security warnings to users.

MitigationApply the Microsoft security updates for CVE-2024-21351 to address this vulnerability. Ensure Windows systems are patched through standard update management processes and verify SmartScreen protections are functioning post-patch.

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
Windows 10 1507Operating system
Affected:< 10.0.10240.20469
Windows 10 1607Operating system
Affected:< 10.0.14393.6709
Windows 10 1809Operating system
Affected:< 10.0.17763.5458
Windows 10 21h2Operating system
Affected:< 10.0.19044.4046
Windows 10 22h2Operating system
Affected:< 10.0.19045.4046
Windows 11 21h2Operating system
Affected:< 10.0.22000.2777
Windows 11 22h2Operating system
Affected:< 10.0.22621.3155
Windows 11 23h2Operating system
Affected:< 10.0.22631.3155

CVSS 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
Low
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine Windows version and build number
    Open Command Prompt and run 'winver' to see the OS version and build, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' for detailed info
    Affected if The displayed build number falls below any of these thresholds: 10240.20469 (1507), 14393.6709 (1607), 17763.5458 (1809), 19044.4046 (21h2), 19045.4046 (22h2), 22000.2777 (Win11 21h2), 22621.3155 (Win11 22h2), or 22631.3155 (Win11 23h2)
  2. Identify Windows 10 release version
    Run 'winver' and note the release (such as 1507, 1607, 1809, 21h2, or 22h2) shown in the about window
    Affected if The release is 1507, 1607, 1809, 21h2, or 22h2 and the corresponding build number is below the patched version for that release as listed in the CVE affected versions
  3. Confirm Windows 11 version
    Run 'winver' - Windows 11 shows as version 22h2 or 23h2 in the about window; check the full build number with 'systeminfo' or 'ver' command
    Affected if Running Windows 11 version 22h2 with build below 22621.3155, or version 23h2 with build below 22631.3155, or version 21h2 with build below 22000.2777
  4. Verify SmartScreen protection status
    Open Windows Security app, go to App and browser control, and check the SmartScreen status for Microsoft Edge and Windows Store apps
    Affected if SmartScreen is enabled in Windows Security (the bypass affects the protection mechanism, so any enabled state means the environment relies on this security feature)

Your environment is affected if the installed Windows version and build number are lower than the patched build for your specific Windows release (10 or 11, including the specific version like 22h2 or 23h2).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.0.10240.20469 / 10.0.14393.6709 / 10.0.17763.5458 or later
Fixed in 10.0.10240.2046910.0.14393.670910.0.17763.5458
Vendor patch msrc.microsoft.com →
Interim mitigation

Apply the Microsoft security updates for CVE-2024-21351 to address this vulnerability. Ensure Windows systems are patched through standard update management processes and verify SmartScreen protections are functioning post-patch.

Recommended fix High confidence

Upgrade to the specific fixed build version for your Windows release as listed above (e.g., Windows 10 22h2: 10.0.19045.4046, Windows 11 23h2: 10.0.22631.3155)

  1. Identify the current Windows version and build number (winver command)
  2. For Windows 10 1507 (build < 10.0.10240.20469): Upgrade to build 10.0.10240.20469 or later
  3. For Windows 10 1607 (build < 10.0.14393.6709): Upgrade to build 10.0.14393.6709 or later
  4. For Windows 10 1809 (build < 10.0.17763.5458): Upgrade to build 10.0.17763.5458 or later
  5. For Windows 10 21h2 (build < 10.0.19044.4046): Upgrade to build 10.0.19044.4046 or later
  6. For Windows 10 22h2 (build < 10.0.19045.4046): Upgrade to build 10.0.19045.4046 or later
  7. For Windows 11 21h2 (build < 10.0.22000.2777): Upgrade to build 10.0.22000.2777 or later
  8. For Windows 11 22h2 (build < 10.0.22621.3155): Upgrade to build 10.0.22621.3155 or later
Caveat Standard Windows update risks apply - ensure backups and test in non-production environments first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-21351 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-21351 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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