CVE-2022-24545
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 · uneditedWindows Kerberos Remote Code Execution Vulnerability
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 confidenceA remote code execution vulnerability exists in the Windows Kerberos implementation. An attacker can exploit this by sending specially crafted Kerberos protocol messages to affected Windows systems, potentially allowing execution of arbitrary code with elevated privileges.
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 data= 20h2= 21h1= 21h2= 1607= 1809= 1909all versionsall versions= 20h2all versionsall versionsCVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify Windows versionRun 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' or 'winver' command to display the installed Windows version and build numberAffected if Version matches Windows 10 (20h2, 21h1, 21h2, 1607, 1809, 1909), Windows 11 (any), Windows Server 2016 (any, 20h2), Windows Server 2019 (any), or Windows Server 2022 (any)
-
Confirm security update installationRun 'wmic qfe list' or 'Get-HotFix' PowerShell cmdlet to list installed hotfixes, then search for the CVE-2022-24545 security updateAffected if The security update for CVE-2022-24545 is NOT installed on the system
-
Verify Kerberos KDC service statusRun 'Get-Service kdc' or 'sc query kdc' to check if the Kerberos Key Distribution Center service is runningAffected if The KDC service is running and the system is a domain controller or has Kerberos authentication enabled
The system is affected if it runs an affected Windows version AND the CVE-2022-24545 security update is not installed AND Kerberos/KDC service is 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.
dbcve · scopedApply Microsoft security updates for CVE-2022-24545 to all affected Windows systems, prioritizing domain controllers and servers running Kerberos KDC service.
February 2022 Security Updates (released Patch Tuesday, February 8, 2022)
- Open Windows Update on the affected system (Settings > Update & Security > Windows Update)
- Click 'Check for updates' to download and install the February 2022 security updates
- Alternatively, download patches from the Microsoft Update Catalog for your specific Windows version
- Restart the system after installing updates
- Verify the update was installed by checking Windows Update history for the February 2022 security updates
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24545 — 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-24545 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