Evidence used
- CISA confirms exploitation in the wild.
- EPSS is 27.80% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2024
CVE-2024-21351High confidence
Microsoft Windows SmartScreen Security Feature Bypass Vulnerability
Microsoft · Windows
7.6HighCVSS 3.1
Patch now
Patch availableCISA confirms exploitation in the wild and lists 2024-03-05 as the remediation due date.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:Critical, raised one band.upgradedsince 13 Feb 2024
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Increase monitoring for the attack path and post-exploitation behaviour described in the report.
Verification
- Confirm that the asset runs Microsoft Windows and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
CISA confirms exploitation in the wild and lists 2024-03-05 as the remediation due date.
Patch available01
What, why and how
Microsoft Windows SmartScreen contains a security feature bypass vulnerability that allows an attacker to bypass the SmartScreen user experience and inject code to potentially gain code execution, which could lead to some data exposure, lack of system availability, or both.
What
Microsoft Windows SmartScreen contains a security feature bypass vulnerability that allows an attacker to bypass the SmartScreen user experience and inject code to potentially gain code execution, which could lead to some data exposure, lack of system availability, or both.
Why
Untrusted data can cross into a code-evaluation path and be interpreted as executable instructions.
How
An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
Microsoft Windows SmartScreen contains a security feature bypass vulnerability that allows an attacker to bypass the SmartScreen user experience and inject code to potentially gain code execution, which could lead to some data exposure, lack of system availability, or both.
Why
Untrusted data can cross into a code-evaluation path and be interpreted as executable instructions.
How
An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation Confirmed in the wild
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.CISA added this CVE to its Known Exploited Vulnerabilities catalogue on 2024-02-13.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Improper Control of Generation of Code ('Code Injection') → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- Required interaction required
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-94 ↗
CWE-94: Improper Control of Generation of Code ('Code Injection'). The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:L/E:U/RL:O/RC:CCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CLowConfidentiality impact: A successful attack can cause a limited loss.IHighIntegrity impact: A successful attack can cause a major loss.ALowAvailability impact: A successful attack can cause a limited loss.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Affected
- Windows 11 version 22H2: 10.0.22621.0 < 10.0.22621.3155
- Windows 10 Version 1607: 10.0.14393.0 < 10.0.14393.6709
- Windows 10 Version 1809: 10.0.17763.0 < 10.0.17763.5458, 10.0.0 < 10.0.17763.5458
- Windows Server 2016: 10.0.14393.0 < 10.0.14393.6709
- Windows 11 Version 23H2: 10.0.22631.0 < 10.0.22631.3155
- Windows Server 2022: 10.0.20348.0 < 10.0.20348.2322
- Windows 11 version 21H2: 10.0.0 < 10.0.22000.2777
- Windows 10 Version 21H2: 10.0.19043.0 < 10.0.19044.4046
- Windows 10 Version 1507: 10.0.10240.0 < 10.0.10240.20469
- Windows 11 version 22H3: 10.0.22631.0 < 10.0.22631.3155
- Windows Server 2019: 10.0.17763.0 < 10.0.17763.5458
- Windows 10 Version 22H2: 10.0.19045.0 < 10.0.19045.4046
- Action
- Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 13 Feb 2024 · Last source change 10 Aug 2026, 17:52 UTC · CWE-94 · Improper Control of Generation of Code ('Code Injection')
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2024-19063
Product sourceCISA KEV
Remediation sourceCVE/CNA references
CWE sourceOther authority
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 10.0.10240.0 < 10.0.10240.20469; 10.0.14393.0 < 10.0.14393.6709; 10.0.17763.0 < 10.0.17763.5458; 10.0.0 < 10.0.17763.5458; 10.0.19043.0 < 10.0.19044.4046; 10.0.19045.0 < 10.0.19045.4046; 10.0.0 < 10.0.22000.2777; 10.0.22621.0 < 10.0.22621.3155 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- After
- Windows 10 Version 1507: 10.0.10240.0 < 10.0.10240.20469; Windows 10 Version 1607: 10.0.14393.0 < 10.0.14393.6709; Windows 10 Version 1809: 10.0.17763.0 < 10.0.17763.5458, 10.0.0 < 10.0.17763.5458; Windows 10 Version 21H2: 10.0.19043.0 < 10.0.19044.4046; Windows 10 Version 22H2: 10.0.19045.0 < 10.0.19045.4046; Windows 11 version 21H2: 10.0.0 < 10.0.22000.2777; Windows 11 version 22H2: 10.0.22621.0 < 10.0.22621.3155; Windows 11 version 22H3: 10.0.22631.0 < 10.0.22631.3155; Windows 11 Version 23H2: 10.0.22631.0 < 10.0.22631.3155; Windows Server 2016: 10.0.14393.0 < 10.0.14393.6709; Windows Server 2019: 10.0.17763.0 < 10.0.17763.5458; Windows Server 2022: 10.0.20348.0 < 10.0.20348.2322 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
CVE published
Added to CISA KEV
Fixed release or patch reference recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.