Microsoft Windows Mark of the Web (MOTW) Security Feature Bypass
CVE-2022-41091 is a medium-severity incorrect authorization vulnerability in Windows 10 Version 1507 from Microsoft, with a CVSS 3.1 base score of 5.4 out of 10. It can be exploited remotely over the network 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.10240.19567 as the first without the flaw, so updating Windows 10 Version 1507 to that release or later removes the exposure. CISA added it to the Known Exploited Vulnerabilities catalogue on November 8, 2022, which means attacks have been observed in the wild, including in ransomware campaigns.
Attackers are already exploiting this vulnerability, according to CISA.
What to do
- Update Windows 10 Version 1507 to 10.0.10240.19567 or a later version.
- Update Windows 10 Version 1607 to 10.0.14393.5501 or a later version.
- Update Windows 10 Version 1809 to 10.0.17763.3650 or a later version.
- CISA's required action: Apply updates per vendor instructions.
- Read the advisory on msrc.microsoft.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
- 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
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Microsoft | Windows 10 Version 1507 | 10.0.10240.0 up to, but not including, 10.0.10240.19567 | 10.0.10240.19567 |
| Microsoft | Windows 10 Version 1607 | 10.0.14393.0 up to, but not including, 10.0.14393.5501 | 10.0.14393.5501 |
| Microsoft | Windows 10 Version 1809 | 10.0.17763.0 up to, but not including, 10.0.17763.3650; 10.0.0 up to, but not including, 10.0.17763.3650 | 10.0.17763.3650 |
| Microsoft | Windows 10 Version 20H2 | 10.0.0 up to, but not including, 10.0.19042.2251 | 10.0.19042.2251 |
| Microsoft | Windows 10 Version 21H1 | 10.0.0 up to, but not including, 10.0.19043.2251 | 10.0.19043.2251 |
| Microsoft | Windows 10 Version 21H2 | 10.0.19043.0 up to, but not including, 10.0.19044.2251 | 10.0.19044.2251 |
| Microsoft | Windows 10 Version 22H2 | 10.0.19045.0 up to, but not including, 10.0.19045.2251 | 10.0.19045.2251 |
| Microsoft | Windows 11 version 21H2 | 10.0.0 up to, but not including, 10.0.22000.1219 | 10.0.22000.1219 |
| Microsoft | Windows 11 version 22H2 | 10.0.22621.0 up to, but not including, 10.0.22621.819 | 10.0.22621.819 |
| Microsoft | Windows Server 2016 | 10.0.14393.0 up to, but not including, 10.0.14393.5501 | 10.0.14393.5501 |
| Microsoft | Windows Server 2016 (Server Core installation) | 10.0.14393.0 up to, but not including, 10.0.14393.5501 | 10.0.14393.5501 |
| Microsoft | Windows Server 2019 | 10.0.17763.0 up to, but not including, 10.0.17763.3650 | 10.0.17763.3650 |
| Microsoft | Windows Server 2019 (Server Core installation) | 10.0.17763.0 up to, but not including, 10.0.17763.3650 | 10.0.17763.3650 |
| Microsoft | Windows Server 2022 | 10.0.20348.0 up to, but not including, 10.0.20348.1249 | 10.0.20348.1249 |
| Microsoft | Windows 10 1507 | before 10.0.10240.19567 | 10.0.10240.19567 |
| Microsoft | Windows 10 1607 | before 10.0.14393.5501 | 10.0.14393.5501 |
| Microsoft | Windows 10 1809 | before 10.0.17763.3650 | 10.0.17763.3650 |
| Microsoft | Windows 10 20h2 | before 10.0.19042.2251 | 10.0.19042.2251 |
| Microsoft | Windows 10 21h1 | before 10.0.19043.2251 | 10.0.19043.2251 |
| Microsoft | Windows 10 21h2 | before 10.0.19044.2251 | 10.0.19044.2251 |
| Microsoft | Windows 10 22h2 | before 10.0.19045.2251 | 10.0.19045.2251 |
| Microsoft | Windows 11 21h2 | before 10.0.22000.1219 | 10.0.22000.1219 |
| Microsoft | Windows 11 22h2 | before 10.0.22621.819 | 10.0.22621.819 |
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
- NetworkCan be exploited remotely over a network, including the internet.
- 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:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L. Scored by CNA (microsoft.com).
Official description
Windows Mark of the Web 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.
Timeline
- Added to CISA's Known Exploited Vulnerabilities catalogue.
- CVE record published.
- Deadline for US federal agencies to remediate, set by CISA.
- CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-41091US Government Resource
Other vulnerabilities in Windows 10 Version 1507
- 7.0 High severity
- 7.8 High severity
- 7.0 High severity
- 7.7 High severity
- 7.0 High severity
Recent Incorrect Authorization vulnerabilities
- 9.8 Critical severity
- 9.8 Critical severity
- 8.8 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.