CVE-2022-21913
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedLocal Security Authority (Domain Policy) Remote Protocol Security Feature Bypass
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis vulnerability in the Local Security Authority (Domain Policy) Remote Protocol allows a security feature bypass, likely enabling an attacker to circumvent authentication or policy enforcement mechanisms in Active Directory domain environments.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versions= 20h2= 21h1= 21h2= 1607= 1809= 1909all versionsall versionsall versionsall versions= 20h2= 2022all versions= r2all versions= r2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Windows versionRun `winver` or `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"` to identify the installed Windows versionAffected if The version matches any of the affected versions: Windows 10 (all versions, specifically 20h2, 21h1, 21h2, 1607, 1809, 1909), Windows 11 (all versions), Windows 7 (all versions), Windows 8.1 (all versions), Windows Rt 8.1 (all versions), Windows Server 20h2, 2022, 2008 (all versions), 2008 R2, 2012
-
Verify Active Directory domain membershipRun `echo %USERDOMAIN%` or `systeminfo | findstr "Domain"` to determine if the system is joined to an Active Directory domainAffected if The system is joined to an Active Directory domain (shows a domain name different from the workgroup) or is a domain controller itself, as this vulnerability targets LSA in AD environments
-
Confirm LSA service is runningRun `sc query LSASS` or check Services.msc for the Security Accounts Manager (SAM) service statusAffected if The LSASS process (LSA) service is running, which is required for the vulnerability to be exploitable
-
Identify if system is a domain controllerRun `netdom query dc` on a member server or check registry key `HKLM\SYSTEM\CurrentControlSet\Services\NTDS\Parameters` for presence, or run `systeminfo | findstr "Domain Controller"`Affected if The system is a Windows Domain Controller or a member server in an AD domain, as the LSA Domain Policy protocol is used in these environments
A system is affected if it runs any of the listed Windows versions and participates in an Active Directory domain environment with the LSA service active.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the relevant Microsoft security update for CVE-2022-21913 to all affected Windows systems, particularly domain controllers and servers running LSA services.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21913 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-21913 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data