CVE-2021-36942: Microsoft Windows Local Security Authority (LSA) Spoofing
Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2021-11-03.
- CVSS v3.1 (CVE record)
- 7.5
- high
- EPSS (exploit probability, 30 days)
- 66%
- higher than 99.2% of all CVEs
- Added to CISA KEV
- 2021-11-03
- US federal due date 2021-11-17
- Automatable (CISA SSVC)
- yes
- technical impact: total
CVE-2021-36942 explained
CVE-2021-36942 is a spoofing vulnerability in the Microsoft Windows Local Security Authority (LSA). An unauthenticated attacker can call a method on the LSARPC interface and coerce a domain controller to authenticate against another server using NTLM. CISA lists it as known exploited, including in ransomware campaigns, so unpatched domain controllers are a serious risk.
Impact
An attacker needs no credentials and no user interaction, and can reach the flaw over the network with low complexity. The domain controller can be forced to authenticate against another server using NTLM. The confidentiality impact is high. CISA rates the flaw as automatable, meaning it can be exploited at scale, with total technical impact. Attackers are known to use it, including in ransomware campaigns.
Who is affected
The CVE record lists Windows Server 2008 SP2 (fixed in 6.0.6003.21192), 2008 R2 SP1 (fixed in 6.1.7601.25685), 2012 (fixed in 6.2.9200.23435), 2012 R2 (fixed in 6.3.9600.20094), 2016 (fixed in 10.0.14393.4583) and 2019 (fixed in 10.0.17763.2114). Both standard and Server Core installations are affected. Versions below each fixed build are vulnerable. The page lists further products.
Written with AI from the data on this page and checked against it automatically.
Official description
Microsoft Windows Local Security Authority (LSA) contains a spoofing vulnerability allowing an unauthenticated attacker to call a method on the LSARPC interface and coerce the domain controller to authenticate against another server using NTLM.
CISA required action: Apply updates per vendor instructions.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Microsoft Windows Server 2008 R2 Service Pack 1x64AffectedFixed in
- < 6.1.7601.25685
- 6.1.7601.25685
- Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64AffectedFixed in
- < 6.1.7601.25685
- 6.1.7601.25685
- Microsoft Windows Server 2008 Service Pack 232-bit, x64AffectedFixed in
- < 6.0.6003.21192
- 6.0.6003.21192
- Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64AffectedFixed in
- < 6.0.6003.21192
- 6.0.6003.21192
- Microsoft Windows Server 2012x64AffectedFixed in
- < 6.2.9200.23435
- 6.2.9200.23435
- Microsoft Windows Server 2012 (Server Core installation)x64AffectedFixed in
- < 6.2.9200.23435
- 6.2.9200.23435
- Microsoft Windows Server 2012 R2x64AffectedFixed in
- < 6.3.9600.20094
- 6.3.9600.20094
- Microsoft Windows Server 2012 R2 (Server Core installation)x64AffectedFixed in
- < 6.3.9600.20094
- 6.3.9600.20094
- Microsoft Windows Server 2016x64AffectedFixed in
- < 10.0.14393.4583
- 10.0.14393.4583
- Microsoft Windows Server 2016 (Server Core installation)x64AffectedFixed in
- < 10.0.14393.4583
- 10.0.14393.4583
- Microsoft Windows Server 2019x64AffectedFixed in
- < 10.0.17763.2114
- 10.0.17763.2114
- Microsoft Windows Server 2019 (Server Core installation)x64AffectedFixed in
- < 10.0.17763.2114
- 10.0.17763.2114
- Microsoft Windows Server version 2004x64AffectedFixed in
- < 10.0.19041.1165
- 10.0.19041.1165
- Microsoft Windows Server version 20H2x64AffectedFixed in
- < 10.0.19042.1165
- 10.0.19042.1165
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows Server 2008 R2 Service Pack 1x64 |
|
|
| Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2008 Service Pack 232-bit, x64 |
|
|
| Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64 |
|
|
| Microsoft Windows Server 2012x64 |
|
|
| Microsoft Windows Server 2012 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2012 R2x64 |
|
|
| Microsoft Windows Server 2012 R2 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2016x64 |
|
|
| Microsoft Windows Server 2016 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2019x64 |
|
|
| Microsoft Windows Server 2019 (Server Core installation)x64 |
|
|
| Microsoft Windows Server version 2004x64 |
|
|
| Microsoft Windows Server version 20H2x64 |
|
|
How to fix it
- Update to the fixed version for your product:
- Microsoft Windows Server 2008 R2 Service Pack 1: 6.1.7601.25685
- Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation): 6.1.7601.25685
- Microsoft Windows Server 2008 Service Pack 2: 6.0.6003.21192
- Microsoft Windows Server 2008 Service Pack 2 (Server Core installation): 6.0.6003.21192
- Microsoft Windows Server 2012: 6.2.9200.23435
- Microsoft Windows Server 2012 (Server Core installation): 6.2.9200.23435
- Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2021-36942
- CISA's deadline for US federal agencies: 2021-11-17 (passed) – a useful benchmark for everyone else, too.
What to do
- Apply the Microsoft security updates that bring each Windows Server installation to the fixed build or later.
- Prioritize domain controllers, since the flaw coerces them into NTLM authentication.
- Follow any additional guidance in the Microsoft advisory for this CVE.
- Restrict network access to domain controllers so that only trusted systems can reach them.
- Review domain controllers and authentication logs for signs of compromise, given known ransomware use.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- Yes – attackers can automate it at scale
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-749
Questions about CVE-2021-36942
- Is CVE-2021-36942 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03 and notes known use in ransomware campaigns. The required action is to apply updates per vendor instructions.
- Does an attacker need credentials?
- No. The description states that an unauthenticated attacker can call a method on the LSARPC interface. The CVSS data also shows no privileges and no user interaction are required.
- Which systems should I patch first?
- Domain controllers. The vulnerability coerces the domain controller to authenticate against another server using NTLM, so patch them to the fixed build for their Windows Server version first.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.