Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

microsoft-exchange-client-access-server-information-disclosure #2056

Open
Murat-Guner opened this issue Apr 3, 2024 · 2 comments
Open

microsoft-exchange-client-access-server-information-disclosure #2056

Murat-Guner opened this issue Apr 3, 2024 · 2 comments
Assignees
Labels
Milestone

Comments

@Murat-Guner
Copy link

Hi

Synopsis
The remote mail server is affected by an information disclosure vulnerability.

Description
The Microsoft Exchange Client Access Server (CAS) is affected by an information disclosure vulnerability. A remote, unauthenticated attacker can exploit this vulnerability to learn the server's internal IP address.
An attacker can send a crafted GET request to the Web Server with an empty host header that would expose internal IP Addresses of the underlying system in the header response.

Please add capability to check url write rule for hiding server internal ip as explained below.

https://www.cyberis.com/article/microsoft-exchange-client-access-server-information-disclosure

Thanks

@dpaulson45
Copy link
Member

@Murat-Guner based off that article, that issue is only for IIS and only for unsupported versions of IIS. I don't see the value add to include this into an Exchange Health Checker script.

@RandelP
Copy link

RandelP commented Apr 9, 2024

Hello,

Historically, on our Exchange 2016 setup, we successfully mitigated this vulnerability by implementing a URL rewrite rule. This approach was similar with the recommendations in the article that @Murat-Guner shared. The rule was able to effectively hide our server internal IP address from being disclosed through an empty host header in GET requests.

However, after we upgraded our version to Exchange 2019, we've hit a roadblock. The same URL rewrite rule that served us well in the past now introduces complications. Can you please provide a way to mitigate this vulnerability?

@lusassl-msft lusassl-msft self-assigned this Apr 9, 2024
@dpaulson45 dpaulson45 added this to the Backlog milestone Apr 18, 2024
@dpaulson45 dpaulson45 added the P2 label Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants