Skip to main content

CVE-2022-41040Microsoft Exchange Server Server-Side Request Forgery Vulnerability

Patch nowHigh8.8Exploited, CISA due date 2022-10-21EPSS 100%, higher than 100% of scored CVEs

CVE-2022-41040 is a server-side request forgery in Microsoft Exchange Server, rated high (8.8 on CVSS 3.1).

Why this priority: Exploited in the wild: listed in CISA's KEV catalog.

Published · Updated · NVD status: Analyzed

What it is

The server can be made to fetch an address of the attacker's choosing, including internal services and cloud metadata endpoints.

How it is reached

An attacker can exploit it over the network, with an ordinary user account, and nobody has to click anything.

What an attacker gains

A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker make the server send requests into internal networks or cloud metadata.

Is it being exploited?

CISA added it to the Known Exploited Vulnerabilities catalog on 2022-09-30: it is being exploited in the wild. CISA links it to ransomware campaigns. EPSS estimates a 100% chance of exploitation activity in the next 30 days, higher than 100% of scored CVEs.

What to do

  1. Treat it as urgent: it is on CISA's KEV list. CISA's deadline for US federal agencies: 2022-10-21.
  2. Apply the update for your edition of Microsoft Exchange Server. Fixed builds: Microsoft Exchange Server 2013 Cumulative Update 23: 15.00.1497.044; Microsoft Exchange Server 2016 Cumulative Update 22: 15.01.2375.037; Microsoft Exchange Server 2019 Cumulative Update 11: 15.02.0986.036; Microsoft Exchange Server 2019 Cumulative Update 12: 15.02.1118.020; Microsoft Exchange Server 2016 Cumulative Update 23: 15.01.2507.016. The patch notes are linked below.
  3. Until it is patched, review who holds accounts that can reach it.
  4. Check exposed instances for signs of compromise, not only for the version.

Description from NVD

Microsoft Exchange Server Elevation of Privilege Vulnerability

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Services that fetch URLs or call other hosts for a caller. The flaw sits between the application and the internal network behind it.

Trust boundaries in play

  • Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
  • Between the application and the internal network behind it. An attacker who crosses it can make the server send requests into internal networks or cloud metadata.

Questions to answer about your own systems

  • Where does Microsoft Exchange Server run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.