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

nmap script question/clarification [Issue] #158

Closed
jakewalkeruct opened this issue Mar 8, 2021 · 2 comments
Closed

nmap script question/clarification [Issue] #158

jakewalkeruct opened this issue Mar 8, 2021 · 2 comments
Assignees
Labels
question Further information is requested Security

Comments

@jakewalkeruct
Copy link

jakewalkeruct commented Mar 8, 2021

This is a clarification question more so than an issue.

In the text of the http-vuln-cve2021-26855.nse file it provides sample output of:

-- @output
-- PORT STATE SERVICE
-- 443/tcp open https
-- | http-vuln-cve2021-26855:
-- | VULNERABLE
-- | Exchange Server SSRF Vulnerability
-- | State: VULNERABLE
-- | IDs: CVE:CVE-2021-26855
-- |
-- | Disclosure date: 2021-03-02
-- | References:
-- | http://aka.ms/exchangevulns

Does that mean if I do not get this output my server is not vulnerable? Sorry, I am an nmap noob.

When I ran the script I got this output:

Starting Nmap 7.91 ( https://nmap.org ) at 2021-03-08 14:42 US Mountain Standard Time
Nmap scan report for myserver.mydomain.local (10.1.2.108)
Host is up (0.0045s latency).

PORT STATE SERVICE
443/tcp open https
MAC Address: 02:50:41:00:00:02 (Unknown)

Nmap done: 1 IP address (1 host up) scanned in 8.92 seconds

Since I did not get the additional output under the "443/tcp" line does that mean I am good?

@dpaulson45 dpaulson45 added question Further information is requested Security and removed Issue labels Mar 8, 2021
@it-notify
Copy link

it-notify commented Mar 8, 2021

I have the same issue.

Output returns the same info as jakewalkeruct

Is this the expected behavior? I only see an output in the script for a positive vulnerable state so I am assuming that this is expected behavior and secure systems will only report 443 as open.

Please confirm.

@justinhendricksmsft
Copy link
Contributor

justinhendricksmsft commented Mar 9, 2021

Correct, it only outputs "VULNERABLE" if it's vulnerable. If it only shows open then it's not vulnerable. Next update, I'll try to output NOT VULNERABLE to make this more clear.

dpaulson45 added a commit that referenced this issue Apr 21, 2021
Update Logman collection of Experfwiz and Exmon
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested Security
Projects
None yet
Development

No branches or pull requests

6 participants