LiveActive security incident?Get immediate response
CVE Record

CVE-2024-21351: Windows SmartScreen Security Feature Bypass Vulnerability

Windows SmartScreen Security Feature Bypass Vulnerability

HighCVSS 7.6Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This flaw can let an attacker bypass Windows SmartScreen protections after a user interacts with malicious content. Successful exploitation may enable unauthorized code execution or system changes. Its 7.6 CVSS score and inclusion in CISA’s Known Exploited Vulnerabilities catalog make prompt patching a business priority.

Executive priority

Treat as a high-priority patching item because exploitation is known and no authentication is required. Track remediation to completion, prioritizing frequently used workstations and closing unsupported-system gaps. The user-interaction requirement reduces immediacy compared with fully automatic compromise, but does not justify delay.

Technical view

CVE-2024-21351 is a Windows SmartScreen security-feature bypass affecting the listed Windows 10, Windows 11, and Windows Server releases. CVSS 3.1 rates it 7.6: network-accessible, low complexity, no privileges required, but user interaction is required. Expected impacts are high integrity impact and limited confidentiality and availability impact.

Likely exposure

Exposure is likely where listed Windows versions remain without Microsoft’s corresponding security update. User-operated endpoints are especially relevant because exploitation requires user interaction. The supplied evidence does not establish whether SmartScreen configuration changes exposure or identify specific vulnerable update levels.

Exploitation context

CISA lists CVE-2024-21351 in its Known Exploited Vulnerabilities catalog, supporting active exploitation. The supplied sources do not describe campaign prevalence, attacker groups, delivery methods, or exploitation mechanics, so those details should not be inferred.

Researcher notes

The strongest evidence is the Microsoft advisory, CVSS vector, affected-product list, and CISA KEV status. The bundle does not provide root-cause details, proof-of-concept information, campaign telemetry, update identifiers, or configuration-dependent exposure. Validate those details directly against Microsoft’s advisory before making detection or exception decisions.

Mitigation direction

  • Apply Microsoft’s security update for CVE-2024-21351 across every affected and supported Windows release.
  • Prioritize user-operated endpoints and any affected servers where interactive use occurs.
  • Check current Microsoft guidance for release-specific update identifiers and any additional mitigations.

Validation and detection

  • Inventory devices running each Windows edition and build listed in the advisory.
  • Verify installation of Microsoft’s applicable CVE-2024-21351 security update through endpoint-management reporting.
  • Investigate update failures, excluded devices, and unsupported Windows installations.
  • Review security telemetry for SmartScreen-bypass alerts or related suspicious activity, without assuming absence of alerts proves safety.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-94: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-21351 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.6 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:L/E:U/RL:O/RC:C

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
5Timeline events
2ADP providers
3Source links

CISA KEV status

Status
Known exploited
Source
CISA-ADP
Date added
KEV reference

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: activeAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.6CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:L/E:U/RL:O/RC:C2.84.7microsoft

Vulnerability scoring details

Base CVSS 3.1 score

7.6High
CVSS 3.1 vector shape for CVE-2024-21351Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:L/E:U/RL:O/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. Added to KEVCISA-ADP

    CISA Known Exploited Vulnerabilities metadata lists this CVE as known exploited.

  3. ADP timelineCISA-ADP

    CVE-2024-21351 added to CISA KEV

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvcother:kev
  • 2024-02-13T00:00:00.000Z: CVE-2024-21351 added to CISA KEV
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftWindows 10 Version 150710.0.10240.0Listed
MicrosoftWindows 10 Version 160710.0.14393.0Listed
MicrosoftWindows 10 Version 180910.0.17763.0Listed
MicrosoftWindows 10 Version 180910.0.0Listed
MicrosoftWindows 10 Version 21H210.0.19043.0Listed
MicrosoftWindows 10 Version 22H210.0.19045.0Listed
MicrosoftWindows 11 version 21H210.0.0Listed
MicrosoftWindows 11 version 22H210.0.22621.0Listed
MicrosoftWindows 11 version 22H310.0.22631.0Listed
MicrosoftWindows 11 Version 23H210.0.22631.0Listed
MicrosoftWindows Server 201610.0.14393.0Listed
MicrosoftWindows Server 201910.0.17763.0Listed
MicrosoftWindows Server 202210.0.20348.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-94 · source CWE mapping

Improper Control of Generation of Code ('Code Injection')

Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.