CVE-2023-24880VulnerabilityPublished 14 Mar 2023Updated 21 Oct 2025

CVE-2023-24880: Microsoft Windows 10 Version 1809 · Security Feature Bypass

Affects Microsoft Windows 10 Version 1809Source CVE Database V5

Exploited in the wild · used in ransomware campaigns · KEV due 4 Apr 2023 · 78% EPSS : apply the vendor's fix or mitigations to Microsoft Windows 10 Version 1809 now.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.4Medium

How severe the flaw is on the 0–10 CVSS scale.

KEV deadline: 4 Apr 2023 US federal agencies must patch by this date; a sensible deadline for everyone else.
Ransomware: Used in ransomware campaigns
EPSS: 78.0% chance of exploitation in 30 days – higher than 99% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Base metrics

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: Low

Temporal metrics

Exploit Code Maturity: Functional
Remediation Level: Official Fix
Report Confidence: Confirmed

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.
Exploit Code Maturity: Functional: Functional exploit code is available. The code works in most situations where the vulnerability exists.
Remediation Level: Official Fix: A complete vendor solution is available. Either the vendor has issued an official patch, or an upgrade is available.
Report Confidence: Confirmed: Detailed reports exist, or functional reproduction is possible (functional exploits may provide this). Source code is available to independently verify the assertions of the research, or the author or vendor of the affected code has confirmed the presence of the vulnerability.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 14 Mar 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: evidence found.
Listed in CISA KEV the same day as disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE ID reserved
by microsoft
2023-01-3120:32Z, 42 days before disclosure
CVE published
on cve.org
2023-03-1416:55Z, t = 0
Added to CISA KEV (opens in a new tab)
exploitation confirmed · ransomware use known
2023-03-14, the same day as disclosure
KEV remediation due
US federal deadline
2023-04-04, 21 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Apply updates per vendor instructions.

Affected software

Product	Affected	Fixed in
Microsoft Windows 10 Version 1809	Affected =10.0.17763.0	Fixed in–

Description

Windows SmartScreen Security Feature Bypass Vulnerability

Impact

For European organizations, this vulnerability primarily threatens environments still running Windows 10 Version 1809, which may include legacy systems in critical infrastructure, government, or industrial sectors. The bypass of SmartScreen reduces the effectiveness of a key security control designed to prevent execution of untrusted or malicious files, potentially leading to increased risk of malware infections or unauthorized code execution. Although the impact on confidentiality is negligible, integrity and availability could be affected if malicious payloads are executed. Organizations relying on SmartScreen as part of their defense-in-depth strategy may find their security posture weakened. The requirement for local access and user interaction limits remote exploitation but insider threats or social engineering attacks could leverage this vulnerability. The lack of known exploits in the wild reduces immediate risk, but the presence of the vulnerability in legacy systems means it could be targeted in the future, especially in sectors with slower patch cycles or where upgrading OS versions is challenging.

Mitigation

1. Upgrade affected systems from Windows 10 Version 1809 to a supported and patched Windows version to eliminate the vulnerability entirely. 2. If upgrading is not immediately feasible, consider disabling the SmartScreen feature temporarily to prevent bypass exploitation, but only if alternative security controls are in place. 3. Enforce strict principle of least privilege to limit local user access and reduce the attack surface. 4. Implement application whitelisting and endpoint detection and response (EDR) solutions to detect and block suspicious activities that SmartScreen would normally catch. 5. Educate users on the risks of interacting with untrusted files and the importance of cautious behavior to mitigate social engineering vectors. 6. Monitor local system logs and security events for unusual SmartScreen bypass attempts or related anomalies. 7. Regularly review and update security policies to ensure legacy systems are identified and prioritized for remediation. 8. Coordinate with IT asset management to identify all devices running Windows 10 Version 1809 and track their upgrade status.

CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Oct 2025, 22:56 UTC

WeaknessesCWE-863

Technical details

References

Community reviews

Related threats