Microsoft Exchange CVE-2022-41082 security patches installed but still vulnerable

Max Bongaerts 20 Reputation points
2023-02-08T07:36:13.5433333+00:00

Hi,

We are facing an problem with an Exchange server which has both KB5019758 and KB5022193 installed but still our vulnerability tool says the Exchange server is vulnerable.. 

Did someone else had this problem or someone knows how to fix this? 

Our tool scans the server with the NMAP NSE script and finds it vulnerable. 

Exchange Server
Exchange Server
A family of Microsoft client/server messaging and collaboration software.
1,350 questions
Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,686 questions
{count} votes

Accepted answer
  1. Yuki Sun-MSFT 41,151 Reputation points Microsoft Vendor
    2023-02-09T04:12:36.9633333+00:00

    Hi @Max Bongaerts ,

    Issue is resolved.

    Glad to know that the issue is resolved!

    Noticed that a same question has been posted in the other forum and was finally resolved by manually applying the URL Rewrite rule (EEMS M1.1 Powershell - inbound). Is this also the solution in your case?

    If yes, since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others", I'll repost the solution in case you'd like to "Accept" the answer. If I have misunderstood anything or your solution is not this one, feel free to post back.

    [How do you stop Teams putting all users on hold when accessing documents?]

    Issue Symptom:

    "We are facing an problem with an Exchange server which has both KB5019758 and KB5022193 installed but still our vulnerability tool says the Exchange server is vulnerable."

    Solution:

    "For some reason there was nu URL Rewrite rule (EEMS M1.1 Powershell - inbound), but other exchange servers we manage do have this rule.

    After manually applying the rule I ran an vulnerability scan with our tool and it says it isn't vulnerable anymore. "


1 additional answer

Sort by: Most helpful
  1. Max Bongaerts 20 Reputation points
    2023-02-09T07:06:07.67+00:00

    Yes, that other question is me :)

    Issue is resolved with the Powershell EEMS rule.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.