CVE-2022-41082
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 · uneditedMicrosoft 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 · moderate confidenceThis is a remote code execution vulnerability in Microsoft Exchange Server. The vulnerability allows an attacker to execute arbitrary code on the affected Exchange server, potentially leading to complete system compromise.
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= 2013= 2016= 2019CVSS 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
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Exchange Server installation and versionRun the following command in Exchange Management Shell: Get-ExchangeServer | Select-Object Name, AdminDisplayVersion, BuildNumber. Alternatively, check the Exchange install path (typically C:\Program Files\Microsoft\Exchange Server\V15\) and review bin\Microsoft.Exchange.Configuration.RemoteSessions.exe or other bin files for version information.Affected if The installed version corresponds to Exchange Server 2013, 2016, or 2019 (any build).
-
Verify PowerShell remoting is enabledRun 'Get-PSRemoteConfiguration' or check if the PowerShell virtual directory is exposed in IIS (typically under Default Web Site\PowerShell). Also verify WinRM service is running: Get-Service WinRM.Affected if PowerShell remoting is enabled and accessible (this is the attack vector for CVE-2022-41082).
-
Check for suspicious remote PowerShell sessionsRun 'Get-PSSession | Where-Object {$_.State -eq "Opened"}' to list active remote PowerShell sessions. Also review Windows Security Event Log (Event ID 4624) for unexpected remote logins to the Exchange server.Affected if Unexpected or unauthorized remote PowerShell sessions are active or recent authentication events from unfamiliar sources exist.
-
Review Exchange logs for SSRF indicatorsExamine IIS logs (typically in C:\inetpub\logs\LogFiles\) for requests to /powershell endpoint with unusual parameters. Also check Exchange trace logs for 'ProxyLogon' or similar exploitation patterns.Affected if Log entries show requests to PowerShell endpoint from untrusted sources or anomalous patterns consistent with exploitation attempts.
A user is affected if they have Exchange Server 2013, 2016, or 2019 installed with PowerShell remoting exposed and either evidence of exploitation attempts or unpatched status.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply Microsoft security patches for CVE-2022-41082. If immediate patching is not possible, restrict access to vulnerable Exchange endpoints (such as /powershell and /ecp) from untrusted networks.
Exchange Server 2019: November 2022 CU12 or later; Exchange Server 2016: November 2022 CU23 or later; Exchange Server 2013: November 2022 Security Update (KB5018978)
- Identify your current Microsoft Exchange Server version by running: Get-ExchangeServer | Format-List Name,Edition,AdminDisplayVersion
- For Exchange Server 2019: Apply November 2022 Cumulative Update 12 (CU12) or later from the Microsoft Update Catalog
- For Exchange Server 2016: Apply November 2022 Cumulative Update 23 (CU23) or later from the Microsoft Update Catalog
- For Exchange Server 2013: Apply November 2022 Security Update (SU) for your specific build (KB5018978) from the Microsoft Update Catalog
- Ensure Windows Server is fully updated with all latest patches before applying Exchange updates
- Take a full backup of Exchange databases and configuration before applying any updates
- Test the update in a non-production environment first if possible
- Apply the update and restart the server as required
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41082 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-41082 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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