Security Resilience

CVE-2024-21410

Auth Bypass in Microsoft Exchange Server 2016 … 2019

CISA KEVActive ExploitationEUVD ExploitedAuth Bypass
Published
13 February 2024
Modified
17 June 2026
KEV Added
15 February 2024
Patch / advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.13 96th percentile
Risk Priority 97 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-21410 is a critical-severity Improper Authentication (CWE-287) vulnerability in Microsoft Exchange Server. Its CVSS base score is 9.8 (Critical).

Operationally, ranked in the top 4% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.

The strongest mitigations our analysis identified map to IA-2 (Identification and Authentication (Organizational Users)) and IA-3 (Device Identification and Authentication) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

Microsoft Exchange Server contains an elevation of privilege vulnerability tracked as CVE-2024-21410. The flaw carries a CVSS 3.1 base score of 9.8 and is associated with CWE-287, indicating improper authentication handling that can be reached over the network without credentials or user interaction.

An unauthenticated attacker can send specially crafted requests to an affected Exchange server and obtain elevated privileges, resulting in full compromise of confidentiality, integrity, and availability on the target system.

Microsoft has published guidance and patches through its Security Response Center, while CISA lists the vulnerability in its Known Exploited Vulnerabilities catalog, confirming that remediation should follow the vendor’s update instructions.

EPSS for the CVE rose from lower values to a peak of 0.1069 on 2024-12-09 before receding to the current 0.0614, indicating increased exploitation interest several months after disclosure.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Microsoft Exchange Server Elevation of Privilege Vulnerability

CWE(s)
KEV Date Added
15 February 2024

Related Threats

CVEs Like This One

CVE-2020-0688Same product: Microsoft Exchange Serverboth on KEV
CVE-2018-8581Same product: Microsoft Exchange Serverboth on KEV
CVE-2021-31196Same product: Microsoft Exchange Serverboth on KEV
CVE-2021-26857Same product: Microsoft Exchange Serverboth on KEV
CVE-2021-26858Same product: Microsoft Exchange Serverboth on KEV
CVE-2022-41082Same product: Microsoft Exchange Serverboth on KEV
CVE-2022-41080Same product: Microsoft Exchange Serverboth on KEV
CVE-2021-42321Same product: Microsoft Exchange Serverboth on KEV
CVE-2020-17144Same product: Microsoft Exchange Serverboth on KEV
CVE-2023-21529Same product: Microsoft Exchange Serverboth on KEV

Affected Assets

microsoft
exchange server
2016, 2019

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Mandates unique identification and authentication of organizational users before access, directly stopping improper authentication.

Requires unique identification and authentication of devices before establishing connections, preventing unauthenticated device claims.

Mandates unique identification and authentication of non-organizational users, directly addressing the weakness for external actors.

Manages authenticators with verification and secure distribution, reducing opportunities for improper authentication.

Enforces access only after approved authorizations, which presupposes correct authentication has occurred.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

Mandating segregated approval and oversight for non-human identities reduces the chance that weak or orphaned credentials can be exploited for unauthorized authentication.

blocks

A.5.17 directly mandates generation of non-guessable unique secrets, secure transmission, immediate change of defaults/temporary creds, strong password enforcement, no-reuse, and compromise response, which stops most improper-authentication exploits at source; the bounded remainder is non-password authentication methods and sufficiency-of-proof cases (e.g. IA-2/IA-5 enhancements) left to other controls.

blocks

Security requirements specified early and verified through testing drive the consistent implementation of authentication mechanisms, decreasing the likelihood that authentication steps are omitted or incorrectly applied.

blocks

A.8.26 explicitly requires identifying and addressing authentication-related requirements (including level of trust in identity via 8.5 and 5.17) as part of application development or acquisition, which prevents a slice of CWE-287 but leaves the dominant sufficiency-of-proof aspects (IA-2/IA-5) and many implementation defects untouched.

blocks

A.8.27 mandates security-by-design principles (least privilege, default-deny, never-trust/always-verify, MFA, end-to-end encryption of requests, distrust-external-input, secure session control, and explicit authentication/authorization in every layer), which directly stops most improper-authentication flaws from being exploitable; the bounded remainder is insufficient-proof cases that live only in the strength or correctness of the credential itself (IA-5/IA-2 territory).

blocks

A.8.5 directly mandates appropriate-strength authentication techniques, MFA for critical systems, protected log-on procedures, brute-force resistance, no cleartext passwords/transmission, and session controls that stop exploitation of insufficient proof of identity; the bounded remainder is cases where the chosen technique itself is flawed or insufficiently implemented (e.g. weak biometrics without fallback).

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-287, a class-level weakness. Rules are authored against its narrower children: CWE-295, CWE-306.

References