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

Unknown error code returned - 401 #11

Open
kort3x opened this issue Aug 10, 2021 · 7 comments
Open

Unknown error code returned - 401 #11

kort3x opened this issue Aug 10, 2021 · 7 comments

Comments

@kort3x
Copy link

kort3x commented Aug 10, 2021

First of all: Thanks for the script.

I tried it against multiple servers, always getting this error:

nmap -sT -p 443 -P0 --script http-vuln-exchange-proxyshell.nse host.domain.de
Starting Nmap 7.92 ( https://nmap.org ) at 2021-08-10 14:53 Mitteleuropõische Sommerzeit
Nmap scan report for host.domain.de (xxx.xxx.xxx.xxx)
Host is up (0.00s latency).

PORT    STATE SERVICE
443/tcp open  https
|_http-vuln-exchange-proxyshell: Unknown error code returned - 401 - maybe not an Exchange server

I am a complete nmap noob - am i doing it wrong?

@kort3x
Copy link
Author

kort3x commented Aug 10, 2021

nevermind - figured it out

I hadn't customized the script for the domains.

Sorry

@kort3x kort3x closed this as completed Aug 10, 2021
@kort3x
Copy link
Author

kort3x commented Aug 10, 2021

for others:

you have to change the domain in line 29 from test.com to your domain.

@GossiTheDog
Copy link
Owner

huh, you shouldn't need to do that @kort3x

I think I'm going to add 401 as a not vulnerable response code, it looks like some environments give that

@jernejs
Copy link

jernejs commented Aug 10, 2021

Yeah, changing the domain inside the script doesn't affect my output (and all 5 Exchange servers I tested against return 401).

@kort3x
Copy link
Author

kort3x commented Aug 10, 2021

guess i reopen then

@kort3x kort3x reopened this Aug 10, 2021
@kort3x
Copy link
Author

kort3x commented Aug 10, 2021

no idea why behavior changed for me - it now works aganist all servers no matter what domain i use in line 29

@kerobra
Copy link

kerobra commented Aug 13, 2021

I get a 401 on every Exchange 2016 installation that I checked, and a "not vulnerable" only on the Exchange 2013 installations. I have no Exchange 2019 to verify.

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

4 participants