CyberSecBulletin
CVE-2023-24880Exploited in the wildNVD status: Analyzed

Microsoft Windows SmartScreen Security Feature Bypass

CVE-2023-24880 is a medium-severity incorrect authorization vulnerability in Windows 10 Version 1809 from Microsoft, with a CVSS 3.1 base score of 4.4 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists version 10.0.17763.4131 as the first without the flaw, so updating Windows 10 Version 1809 to that release or later removes the exposure. CISA added it to the Known Exploited Vulnerabilities catalogue on March 14, 2023, which means attacks have been observed in the wild, including in ransomware campaigns.

Patch now

Attackers are already exploiting this vulnerability, according to CISA.

What to do

  1. Update Windows 10 Version 1809 to 10.0.17763.4131 or a later version.
  2. Update Windows Server 2019 to 10.0.17763.4131 or a later version.
  3. Update Windows Server 2019 (Server Core installation) to 10.0.17763.4131 or a later version.
  4. CISA's required action: Apply updates per vendor instructions.
  5. Read the advisory on msrc.microsoft.com for workarounds and exact fixed builds.
  6. Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.

Affected products and versions

VendorProductAffected versionsFixed in
MicrosoftWindows 10 Version 180910.0.17763.0 up to, but not including, 10.0.17763.4131; 10.0.0 up to, but not including, 10.0.17763.413110.0.17763.4131
MicrosoftWindows Server 201910.0.17763.0 up to, but not including, 10.0.17763.413110.0.17763.4131
MicrosoftWindows Server 2019 (Server Core installation)10.0.17763.0 up to, but not including, 10.0.17763.413110.0.17763.4131
MicrosoftWindows Server 202210.0.20348.0 up to, but not including, 10.0.20348.160710.0.20348.1607
MicrosoftWindows 10 Version 20H210.0.0 up to, but not including, 10.0.19042.272810.0.19042.2728
MicrosoftWindows 11 version 21H210.0.0 up to, but not including, 10.0.22000.169610.0.22000.1696
MicrosoftWindows 10 Version 21H210.0.19043.0 up to, but not including, 10.0.19044.272810.0.19044.2728
MicrosoftWindows 11 version 22H210.0.22621.0 up to, but not including, 10.0.22621.141310.0.22621.1413
MicrosoftWindows 10 Version 22H210.0.19045.0 up to, but not including, 10.0.19045.272810.0.19045.2728
MicrosoftWindows 10 Version 160710.0.14393.0 up to, but not including, 10.0.14393.578610.0.14393.5786
MicrosoftWindows Server 201610.0.14393.0 up to, but not including, 10.0.14393.578610.0.14393.5786
MicrosoftWindows Server 2016 (Server Core installation)10.0.14393.0 up to, but not including, 10.0.14393.578610.0.14393.5786
MicrosoftWindows 10 1607before 10.0.14393.578610.0.14393.5786
MicrosoftWindows 10 1809before 10.0.17763.413110.0.17763.4131
MicrosoftWindows 10 20h2before 10.0.19042.272810.0.19042.2728
MicrosoftWindows 10 21h2before 10.0.19044.272810.0.19044.2728
MicrosoftWindows 10 22h2before 10.0.19045.272810.0.19045.2728
MicrosoftWindows 11 21h2before 10.0.22000.169610.0.22000.1696
MicrosoftWindows 11 22h2before 10.0.22000.141310.0.22000.1413

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
RequiredA user must take an action such as opening a file or link.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
LowLimited modification of data is possible.
Availability
LowPerformance or availability is reduced.

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.14.4MediumCNA (microsoft.com)
CVSS 3.14.4MediumNVD

Official description

Windows SmartScreen Security Feature Bypass Vulnerability

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Incorrect Authorization

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.

How developers prevent this class of flaw

  • 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. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
  • 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. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.

More Incorrect Authorization vulnerabilities (CWE-863)

Timeline

  1. CVE record published.
  2. Added to CISA's Known Exploited Vulnerabilities catalogue.
  3. Deadline for US federal agencies to remediate, set by CISA.
  4. CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: partial).
  5. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Recent Incorrect Authorization vulnerabilities

Spotted an error? Tell us.