CVE-2024-20674Windows Kerberos security feature bypass, impersonate the KDC
What broke
Windows Kerberos let an unauthenticated attacker on the network impersonate the Kerberos server (security feature bypass). Machine-in-the-middle, no prior account. CVSS 8.8. Microsoft patched it on 9 January 2024.
Why it matters
If you can impersonate the KDC, you can issue tickets. That is domain identity, not a workstation bug. Read it as the start of the 2024-2026 Kerberos train: PAC validation, PKINIT, CheckSum, KerberLoss.
What to do
- Deploy January 2024 updates on DCs and on members that speak Kerberos.
- Prefer SMB signing and channel binding so a forged KDC conversation is harder to land.
- Watch for unexpected KDC referrals and TGT requests that do not match your DC inventory.
After you patch
Active Directory compromise is not contained by patching, because the artifacts an attacker creates outlive the vulnerability.
- Rotate the krbtgt account twice, with the replication interval between rotations, if there is any indication of ticket forgery. One rotation is not enough.
- Audit AD CS certificate templates for enrolment and enrollee-supplied-subject permissions, which are the most common escalation path left behind. See certificate lifecycle.
- Review privileged group membership and delegation rights (Domain Admins, DnsAdmins, constrained and resource-based constrained delegation) for changes during the window.
- Hunt for tickets with anomalous lifetimes or encryption types, and for authentications to services that identity never touches.
- Treat any issued certificate as a durable credential: revoking a user's password does not revoke a certificate that authenticates as them. See privilege escalation and lateral movement.
Sources
- NVD: CVE-2024-20674
- Microsoft January 2024 Patch Tuesday
Related identity CVEs
Related on Start with Identity
- CVEWindows Kerberos elevation of privilege
A 2026 Windows Kerberos elevation of privilege, patched by Microsoft. High severity. Read it next to KerberLoss and ResetNightmare: the 2026 AD year is a Kerber
- CVEWindows Kerberos information disclosure
A medium-severity Kerberos information-disclosure in Windows. Not a domain-compromise bug on its own, but it sits in the same 2025 Kerberos patch train as the S
- CVEWindows Kerberos PAC validation in cross-forest scenarios
The forest-trust sibling of CVE-2024-26248. PAC validation could be skipped across a trust. Same April 2024 patch train, same staged enforcement.
- BlogKerberLoss: invisible Unicode lets an attacker twin a Kerberos SPN
CVE-2026-25177, CVSS 8.8. Active Directory treated look-alike SPNs as unique. Semperis and Shai Laron showed how that becomes service hijack and NTLM downgrade.
- BlogA CVE ID is a name. The value is knowing who the attacker becomes.
We opened a practitioner catalog of identity CVEs: what broke, why IAM teams should care, and what to do this week. Not an NVD mirror. A place to triage SAML wr
- BlogGoogle Workspace puts FIDO2 keys into the Windows login, days after Entra makes passkeys default
Google began rolling out FIDO2 security keys as a second factor at Windows sign-in for all Workspace customers on 13 July. Microsoft is making passkeys the defa