dbcve.org
Exchange ServerApplication · Microsoft

CVE-2023-28310

HIGH · 8.0 CVSS v3.1 Published 2023-06-14
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
82/100
Remediation priority · High
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 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
How this class of weakness works · CWE-502

The application rebuilds objects from attacker-supplied serialized data, and the act of rebuilding can trigger dangerous code paths. In many runtimes this leads straight to remote code execution. The durable fix is to avoid deserializing untrusted input — or to use a strict, type-limited format with integrity checks.

General guidance for the deserialization of untrusted data class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 →
Recommended fix High confidence

For full functionality, upgrade to Exchange Server 2016 CU23 or Exchange Server 2019 CU12 as the long-term recommended path

  1. 1. Identify the current Cumulative Update (CU) version installed on the Exchange Server by running: Get-ExchangeServer | Format-List Name,Edition,AdminDisplayVersion
  2. 2. For Exchange Server 2016: Apply Security Update KB5001779 (April 2023) - ensure at minimum CU22 is installed before applying the SU
  3. 3. For Exchange Server 2019: Apply Security Update KB5001779 (April 2023) - ensure at minimum CU11 is installed before applying the SU
  4. 4. Download the appropriate security update from https://www.microsoft.com/download/details.aspx?id=104129
  5. 5. Run the security update as an administrator on the Exchange Server
  6. 6. Restart the server or restart Exchange services after the update completes
  7. 7. Verify the update installed successfully by checking the installed updates: Get-Command ExSetup.exe | ForEach-Object { & $_.Source -Verbose } and confirm the version matches KB5001779
Caveat Security updates typically have minimal breaking changes; however, ensure to review KB5001779 for any known issues before deployment in production environments

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

We can apply and verify the patch for your build — typical engagement from $3,200. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-28310 — 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-2023-28310 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