CVE-2024-21427Network attack vector

Authentication-policy bypass via unenforced AS-REQ silo checks

Published Mar 12, 2024 · Updated May 3, 2025

Improper authentication in Microsoft Windows Server allows remote authenticated users to bypass Active Directory authentication policies. The Key Distribution Center omits authentication-silo checks when processing AS-REQs for service principals other than krbtgt, although those checks already apply to TGS requests. Exploitation requires a low-privilege domain account and specially formed network authentication traffic; successful requests circumvent configured account restrictions and expose protected domain resources.

CVSS severity7.5
High
EPSS probability1.53%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper authentication in Microsoft Windows Server allows remote authenticated users to bypass Active Directory authentication policies. The Key Distribution Center omits authentication-silo checks when processing AS-REQs for service principals other than krbtgt, although those checks already apply to TGS requests. Exploitation requires a low-privilege domain account and specially formed network authentication traffic; successful requests circumvent configured account restrictions and expose protected domain resources.

The record

CVE
CVE-2024-21427
Published
Mar 12, 2024
Updated
May 3, 2025
Vendor
Microsoft
Product
Windows Server 2019
Classifications
CWE-287
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Mar 12, 2024CVE publishedPublication date reported by the CVE source.
  2. May 3, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=10.0.17763.0 <10.0.17763.5696

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Microsoft · Windows Server 2019version=10.0.17763.0 <10.0.17763.5696
Microsoft · Windows Server 2016 (Server Core installation)version=10.0.14393.0 <10.0.14393.6897
Microsoft · Windows Server 2022, 23H2 Edition (Server Core installation)version=10.0.25398.0 <10.0.25398.830
Microsoft · Windows Server 2016version=10.0.14393.0 <10.0.14393.6897
Microsoft · Windows Server 2012 R2 (Server Core installation)version=6.3.9600.0 <6.3.9600.21924
Microsoft · Windows Server 2019 (Server Core installation)version=10.0.17763.0 <10.0.17763.5696
Microsoft · Windows Server 2022version=10.0.20348.0 <10.0.20348.2402
Microsoft · Windows Server 2012 R2version=6.3.9600.0 <6.3.9600.21924

Published CVSS scores

7.5Microsoft CorporationCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-287Improper Authentication

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo