CVE-2022-26925Exploited in the wildNVD status: Analyzed
Microsoft Windows LSA Spoofing
CVE-2022-26925 is a medium-severity missing authentication for critical functionality vulnerability in Windows 10 Version 1809 from Microsoft, with a CVSS 3.1 base score of 5.9 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 10.0.17763.2928 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 July 1, 2022, which means attacks have been observed in the wild.
Patch now
Attackers are already exploiting this vulnerability, according to CISA.
What to do
- Update Windows 10 Version 1809 to 10.0.17763.2928 or a later version.
- Update Windows Server 2019 to 10.0.17763.2928 or a later version.
- Update Windows Server 2019 (Server Core installation) to 10.0.17763.2928 or a later version.
- CISA's required action: Apply remediation actions outlined in CISA guidance [https://www.cisa.gov/guidance-applying-june-microsoft-patch].
- 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.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Microsoft | Windows 10 Version 1809 | 10.0.17763.0 up to, but not including, 10.0.17763.2928; 10.0.0 up to, but not including, 10.0.17763.2928 | 10.0.17763.2928 |
| Microsoft | Windows Server 2019 | 10.0.17763.0 up to, but not including, 10.0.17763.2928 | 10.0.17763.2928 |
| Microsoft | Windows Server 2019 (Server Core installation) | 10.0.17763.0 up to, but not including, 10.0.17763.2928 | 10.0.17763.2928 |
| Microsoft | Windows 10 Version 1909 | 10.0.0 up to, but not including, 10.0.18363.2274 | 10.0.18363.2274 |
| Microsoft | Windows 10 Version 21H1 | 10.0.0 up to, but not including, 10.0.19043.1706 | 10.0.19043.1706 |
| Microsoft | Windows Server 2022 | 10.0.20348.0 up to, but not including, 10.0.20348.707 | 10.0.20348.707 |
| Microsoft | Windows 10 Version 20H2 | 10.0.0 up to, but not including, 10.0.19042.1706 | 10.0.19042.1706 |
| Microsoft | Windows Server version 20H2 | 10.0.0 up to, but not including, 10.0.19042.1706 | 10.0.19042.1706 |
| Microsoft | Windows 11 version 21H2 | 10.0.0 up to, but not including, 10.0.22000.675 | 10.0.22000.675 |
| Microsoft | Windows 10 Version 21H2 | 10.0.19043.0 up to, but not including, 10.0.19043.1706 | 10.0.19043.1706 |
| Microsoft | Windows 10 Version 1507 | 10.0.10240.0 up to, but not including, 10.0.10240.19297 | 10.0.10240.19297 |
| Microsoft | Windows 10 Version 1607 | 10.0.14393.0 up to, but not including, 10.0.14393.5125 | 10.0.14393.5125 |
| Microsoft | Windows Server 2016 | 10.0.14393.0 up to, but not including, 10.0.14393.5125 | 10.0.14393.5125 |
| Microsoft | Windows Server 2016 (Server Core installation) | 10.0.14393.0 up to, but not including, 10.0.14393.5125 | 10.0.14393.5125 |
| Microsoft | Windows 7 | 6.1.0 up to, but not including, 6.1.7601.25954 | 6.1.7601.25954 |
| Microsoft | Windows 7 Service Pack 1 | 6.1.0 up to, but not including, 6.1.7601.25954 | 6.1.7601.25954 |
| Microsoft | Windows 8.1 | 6.3.0 up to, but not including, 6.3.9600.20371 | 6.3.9600.20371 |
| Microsoft | Windows Server 2008 Service Pack 2 | 6.0.6003.0 up to, but not including, 6.0.6003.21481 | 6.0.6003.21481 |
| Microsoft | Windows Server 2008 Service Pack 2 (Server Core installation) | 6.0.6003.0 up to, but not including, 6.0.6003.21481 | 6.0.6003.21481 |
| Microsoft | Windows Server 2008 R2 Service Pack 1 | 6.1.7601.0 up to, but not including, 6.1.7601.25954 | 6.1.7601.25954 |
| Microsoft | Windows Server 2008 R2 Service Pack 1 (Server Core installation) | 6.1.7601.0 up to, but not including, 6.1.7601.25954 | 6.1.7601.25954 |
| Microsoft | Windows Server 2012 | 6.2.9200.0 up to, but not including, 6.2.9200.23714 | 6.2.9200.23714 |
| Microsoft | Windows Server 2012 (Server Core installation) | 6.2.9200.0 up to, but not including, 6.2.9200.23714 | 6.2.9200.23714 |
| Microsoft | Windows Server 2012 R2 | 6.3.9600.0 up to, but not including, 6.3.9600.20371 | 6.3.9600.20371 |
| Microsoft | Windows Server 2012 R2 (Server Core installation) | 6.3.9600.0 up to, but not including, 6.3.9600.20371 | 6.3.9600.20371 |
Version data comes from the organisation that assigned the CVE; 11 further products are omitted here. 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
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.1 | High | CNA (microsoft.com) |
| CVSS 3.1 | 5.9 | Medium | NVD |
| CVSS 2.0 | 4.3 | Medium | NVD |
Official description
Windows LSA Spoofing Vulnerability
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Authentication for Critical Functionality
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
How developers prevent this class of flaw
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- 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 libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator.
- When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to require strong authentication for users who should be allowed to access the data.
More Missing Authentication for Critical Functionality vulnerabilities (CWE-306)
Timeline
- CVE record published.
- Added to CISA's Known Exploited Vulnerabilities catalogue.
- Deadline for US federal agencies to remediate, set by CISA.
- CISA published its SSVC assessment (exploitation: active, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Third-party and government advisories
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-26925US Government Resource
Recent Missing Authentication for Critical Functionality vulnerabilities
- 9.8 Critical severity
F5 BIG-IP Missing Authentication Exploited
- 7.5 High severity
- 7.8 High severity
- 9.8 Critical severity
- 9.1 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.