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

Exchange 2019 potentially vulnerable, check latest security update is applied (Exchange 2019 CU7 or CU8 installed) #6

Open
jamesraay opened this issue Mar 12, 2021 · 5 comments

Comments

@jamesraay
Copy link

All servers have the latest CU and the security patch installed. What does this message mean?

|_http-server-header: Microsoft-IIS/10.0
|_http-vuln-exchange: (15.2.792) Exchange 2019 potentially vulnerable, check latest security update is applied (Exchange 2019 CU7 or CU8 installed)

For all other scans I get "Error 403 for /owa" or similar.

@lukastribus
Copy link

"Potentially vulnerable" means that this script cannot determine anything (because it's just looking at the version, which is not saying anything). Also see #4

I strongly suggest people use Microsoft's nmap script instead, which does proper detection:

https://github.com/microsoft/CSS-Exchange/blob/main/Security/src/http-vuln-cve2021-26855.nse

@jamesraay
Copy link
Author

jamesraay commented Mar 14, 2021 via email

@jamesraay
Copy link
Author

jamesraay commented Mar 14, 2021 via email

@lukastribus
Copy link

PS C:\users\james\documents\nmapscripts> nmap -p 443 --script .\http-vuln-exchange.nse MBX01.domain.net
Starting Nmap 7.91 ( https://nmap.org ) at 2021-03-14 11:49 Pacific Daylight Time
Nmap scan report for MBX01.domain.net (192.168.1.10)
Host is up (0.0010s latency).

PORT    STATE SERVICE
443/tcp open  https
MAC Address: 00:0C:29:00:99:AF (VMware)

Nmap done: 1 IP address (1 host up) scanned in 0.85 seconds
PS C:\users\james\documents\nmapscripts>

I assume this means it is NOT vulnerable?

Correct.

@jamesraay
Copy link
Author

jamesraay commented Mar 14, 2021 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants