CVE-2024-29988

SmartScreen Prompt Security Feature Bypass Vulnerability

HIGH
8.8
CVSS Score
Published: April 9, 2024 at 05:00 PM UTC
Updated: June 17, 2026 at 07:23 AM UTC
10 products affected across 1 vendorWindows Server 2019Windows 10 1809Windows Server 2022

Using Windows 10 Version 1809 by Microsoft?

Get instant alerts when new vulnerabilities affect Windows 10 Version 1809 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploitation
CISA KEV
Exploit prediction
EPSS 45%
SSVC
Active

Actively Exploited

CISA Known Exploited Vulnerabilities (KEV) Catalog

EPSS Score45.2%

EPSS (Exploit Prediction Scoring System) estimates a 45.2% chance this CVE is exploited in the wild within the next 30 days — higher than 99% of all CVEs. It complements CVSS: a high EPSS on a mid-severity CVE can still be urgent.

Microsoft SmartScreen Prompt contains a security feature bypass vulnerability that allows an attacker to bypass the Mark of the Web (MotW) feature. This vulnerability can be chained with CVE-2023-38831 and CVE-2024-21412 to execute a malicious file.

Required Action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Ransomware Use
Unknown
Added to KEV
Apr 30, 2024
Remediation Due
May 21, 2024
894 days overdue

Description

SmartScreen Prompt Security Feature Bypass Vulnerability

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 10.0.17763.569610.0.0 ≤ v < 10.0.17763.569610.0.17763.0 ≤ v < 10.0.17763.569610.0.010.0.17763.0
Affected range stops below 10.0.17763.5696, so it looks safe — our inference, not a vendor statement
v < 10.0.19044.429110.0.19043.0 ≤ v < 10.0.19044.429110.0.19043.0
Affected range stops below 10.0.19044.4291, so it looks safe — our inference, not a vendor statement
v < 10.0.19045.429110.0.19045.0 ≤ v < 10.0.19045.429110.0.19045.0
Affected range stops below 10.0.19045.4291, so it looks safe — our inference, not a vendor statement
v < 10.0.22000.289910.0.0 ≤ v < 10.0.22000.289910.0.0
Affected range stops below 10.0.22000.2899, so it looks safe — our inference, not a vendor statement
v < 10.0.22621.344710.0.22621.0 ≤ v < 10.0.22621.344710.0.22621.0
Affected range stops below 10.0.22621.3447, so it looks safe — our inference, not a vendor statement
v < 10.0.22631.344710.0.22631.0 ≤ v < 10.0.22631.344710.0.22631.0
Affected range stops below 10.0.22631.3447, so it looks safe — our inference, not a vendor statement
v < 10.0.17763.569610.0.17763.0 ≤ v < 10.0.17763.569610.0.17763.0
Affected range stops below 10.0.17763.5696, so it looks safe — our inference, not a vendor statement
v < 10.0.20348.240210.0.20348.0 ≤ v < 10.0.20348.240210.0.20348.0
Affected range stops below 10.0.20348.2402, so it looks safe — our inference, not a vendor statement
v < 10.0.25398.83010.0.25398.0 ≤ v < 10.0.25398.83010.0.25398.0
Affected range stops below 10.0.25398.830, so it looks safe — our inference, not a vendor statement
10.0.25398.0 ≤ v < 10.0.25398.830
Affected range stops below 10.0.25398.830, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCActiveNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.8HIGHmicrosoft
Vector?

Quick Info

StatusANALYZED
CWE
CWE-693NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card