dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 7 Mar 2024.
Exchange ServerApplication · Microsoft

CVE-2024-21410

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-13
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable No privileges Zero-click Patch available

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 · unedited
Microsoft Exchange Server Elevation of Privilege 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 confidence

Microsoft Exchange Server contains an elevation of privilege vulnerability. The CVSS 9.8 indicates this allows an unauthenticated attacker to gain high-level privileges, likely administrative access, through network exploitation.

MitigationApply Microsoft Exchange Server security updates immediately. Review Microsoft advisory for specific patch versions and any recommended configuration changes.

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
Exchange ServerApplication
Affected:= 2016= 2019

CVSS 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
High
Availability
High

CVSS:3.1/AV:N/AC:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Exchange Server version
    Run 'Get-ExchangeServer | Format-List Name, Edition, AdminDisplayVersion' in Exchange Management Shell, or check the installed version via Control Panel > Programs and Features > Microsoft Exchange Server
    Affected if Version matches Exchange Server 2016 or 2019 (compare your exact build number to the affected version ranges)
  2. Check Exchange services status
    Run 'Get-Service MSExchange* | Select-Object Name, Status' in Exchange Management Shell to confirm Exchange services are running
    Affected if Exchange services are active and the server version falls within affected versions
  3. Verify patch installation status
    Run 'Get-Command ExSetup | ForEach-Object { & $_.Source } /Version' or check Windows Update history for recent Exchange security updates
    Affected if No recent Exchange security updates installed or patches missing for CVE-2024-21410
  4. Review Exchange administrative access
    Check for unexpected administrators or role groups via 'Get-RoleGroupMember "Organization Management"' and review 'Get-ExchangeServer | Select-Object AdminDisplayVersion'
    Affected if Server is on vulnerable version AND has active Exchange services with unpatched status

A user is affected if their Exchange Server 2016 or 2019 installation is running a vulnerable build without the CVE-2024-21410 security update applied.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Patch available Apply the vendor patch
Vendor patch msrc.microsoft.com →
Interim mitigation

Apply Microsoft Exchange Server security updates immediately. Review Microsoft advisory for specific patch versions and any recommended configuration changes.

Recommended fix High confidence

Exchange Server 2016 CU23 or Exchange Server 2019 CU14 (latest respective CU)

  1. 1. Identify current Exchange Server version by running: Get-ExchangeServer | Format-List Name,Edition,AdminDisplayVersion
  2. 2. If running Exchange Server 2016, upgrade to Cumulative Update 23 or later
  3. 3. If running Exchange Server 2019, upgrade to Cumulative Update 14 or later
  4. 4. Ensure backup of Exchange databases and configuration is completed before applying updates
  5. 5. Schedule maintenance window as Exchange CU updates require server downtime
  6. 6. Install the appropriate cumulative update following Microsoft documentation
  7. 7. Verify Exchange services are running properly post-upgrade
  8. 8. Test mail flow and Outlook connectivity
Caveat Cumulative updates require downtime and proper planning; always test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Exchange Server Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-21410 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-21410 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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