Microsoft Exchange Server Privilege Escalation Vulnerability
Exploited since 2021-11-03. 1 of 8 rule sources name it.
Microsoft Exchange Server Elevation of Privilege Vulnerability
Edge coverage
Claimed by vendorsAsk Vigil
AI · answers from this pageWorkers AI (Llama 3.3). Can be wrong: check the cited source.
Severity, decoded
CVSS 3.1Exploitable with local access, with no privileges and no user interaction, leading to full loss of confidentiality and integrity, and the impact can reach components beyond the vulnerable one.
How the score is built
- Attack vectorAn attacker needs local access, or must trick a user into opening something on the machine.Local
- Attack complexityNo special conditions are needed; the attack works reliably.Low
- Privileges requiredNo account or login is needed.None
- User interactionNo one has to click or open anything; the attack works on its own.None
- ScopeThe attack can spread beyond the vulnerable component to other parts of the system.Changed
- Confidentiality impactAn attacker can read all data the affected component holds, or the most sensitive parts of it.High
- Integrity impactAn attacker can change any data or files the affected component protects.High
- Availability impactThe component keeps working normally.None
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N/E:U/RL:O/RC:CAlso in the vector: Exploit code maturity: Unproven · Remediation level: Official fix · Report confidence: Confirmed
Attackers are exploiting this in the wild.
At least one step needs hands-on work, which slows mass attacks.
A successful attack gives full control over the affected software or all of its data.
Public exploits
1 found- MetasploitMicrosoft Exchange ProxyShell RCE2021-04-06 · exploit · rank Excellent · has check
Links are to third-party code: never run it outside an isolated lab.
Timeline
- 2021-04-06Metasploit module publishedMicrosoft Exchange ProxyShell RCE
- 2021-07-14CVE publishedCVE List
- 2021-11-03Added to CISA KEVConfirmed exploitation in the wild
- 2024-01-16F5 rule names itEarliest entry we can see is an update
Vendor statements
QuotedCloudflareWAF Managed Rules
The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.
AWSAWS WAF Managed Rules
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. AWS often describes a vulnerability without naming its CVE (for example "Log4j"). We count only entries that name the CVE, so AWS coverage is understated.
Microsoft AzureFront Door and Application Gateway WAF (DRS)
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. The rule tables name CVEs but carry no dates, so Azure is left out of every time-to-rule figure.
Google CloudCloud Armor preconfigured WAF rules
The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.
FastlyNext-Gen WAF virtual patches
The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.
F5Attack signatures (Distributed Cloud WAF)
Named by 2024-01-16; the first entry is an update, so the rule may be older.
Updated: signature 200018136 "Microsoft Exchange ProxyShell Privilege Escalation" (Other Application Attacks, risk High), systems: Outlook Web Access. References: CVE-2021-34523.
AkamaiApp & API Protector (Adaptive Security Engine)
This vendor publishes no machine-readable rule changelog we can check.
OWASP CRSCore Rule Set (open source, used inside many WAFs)
The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.
Social
No posts seen yet on X, Bluesky, Mastodon, Hacker News or GitHub.