Outdated Microsoft Exchange Server
An on-premises Exchange server is missing Microsoft's security updates, runs a cumulative update too old to receive them, or runs an unsupported release.
| Severity | Critical |
| CVSS 3.1 | 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Open in the calculator |
| CVSS 4.0 | 9.3 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-1395: Dependency on Vulnerable Third-Party Component |
| OWASP Top 10 | A03:2025 Software Supply Chain Failures |
| MITRE ATT&CK | T1190 Exploit Public-Facing Application, T1210 Exploitation of Remote Services |
| Category | Outdated Components |
Description
An on-premises Microsoft Exchange Server is missing security updates (SUs) that Microsoft has released, runs a cumulative update (CU) too old to receive them, or runs an Exchange release that has passed the end of its support. Microsoft releases SUs only for the most recent one or two CUs of each release, so a server on an older CU cannot be secured until its CU is updated.
Exchange servers are a frequent target because they are usually reachable from the internet through Outlook on the web, ActiveSync and Autodiscover, hold extensive rights in Active Directory, and store the organisation's email, and unpatched servers have been mass-exploited repeatedly. Flaws such as ProxyLogon (CVE-2021-26855) and ProxyShell (CVE-2021-34473) let unauthenticated attackers on the internet run code on the server as SYSTEM, read any mailbox and install web shells, and are listed in CISA's Known Exploited Vulnerabilities (KEV) catalogue. Because of the server's high privileges in Active Directory, its compromise commonly leads to compromise of the domain, alongside theft of the organisation's email. Several Exchange flaws have been exploited before a fix was released or within days of one, so any delay is particularly dangerous for internet-facing servers.
The finding is identified by an authenticated scan that reads the installed build, by Microsoft's Exchange Server Health Checker script, or remotely from the build number that Outlook on the web and other endpoints expose, and scanners report one result per missing update. Some updates also require manual steps after installation, such as enabling Extended Protection or applying configuration changes, which the Health Checker reports separately. Hybrid deployments often keep an on-premises Exchange server for recipient management, which also needs updating.
Remediation
Bring every Exchange server to a supported, fully updated state:
- Install the latest CU for the Exchange release in use, then the latest SU for that CU, on every Exchange server, including hybrid management servers, following Microsoft's update guidance.
- Run the Exchange Server Health Checker after updating and complete any manual actions it reports, such as enabling Extended Protection.
- Migrate servers running an Exchange release that has passed end of support to a supported release or to Exchange Online.
- Limit internet exposure to the services users need, publish them through a pre-authenticating gateway where possible, and never expose remote PowerShell or the Exchange administration interfaces to the internet.
- Where an update cannot be installed immediately, apply Microsoft's published mitigation for the specific vulnerability, which the Exchange Emergency Mitigation service can apply automatically on supported builds, and check the servers for indicators of compromise.
Confirm the fix by running the Health Checker and checking that each server reports the latest SU with no outstanding actions.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.