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

smb-vuln-ms17-010.nse threw an error! is this expected? #13

Open
sssseossss opened this issue Sep 5, 2017 · 3 comments
Open

smb-vuln-ms17-010.nse threw an error! is this expected? #13

sssseossss opened this issue Sep 5, 2017 · 3 comments
Labels

Comments

@sssseossss
Copy link

Hi,
thanks for a great script. Can you assist in resolving this:
mrp@user:/usr/share/nmap/scripts$ nmap -p445 --script=smb-vuln-ms17-010.nse 192.168.1.9 -d

Starting Nmap 7.01 ( https://nmap.org ) at 2017-09-05 14:24 IST
--------------- Timing report ---------------
hostgroups: min 1, max 100000
rtt-timeouts: init 1000, min 100, max 10000
max-scan-delay: TCP 1000, UDP 1000, SCTP 1000
parallelism: min 0, max 0
max-retries: 10, host-timeout: 0
min-rate: 0, max-rate: 0

NSE: Using Lua 5.2.
NSE: Arguments from CLI:
NSE: Loaded 1 scripts for scanning.
NSE: Script Pre-scanning.
NSE: Starting runlevel 1 (of 1) scan.
Initiating NSE at 14:24
Completed NSE at 14:24, 0.00s elapsed
Initiating Ping Scan at 14:24
Scanning 192.168.1.9 [2 ports]
Completed Ping Scan at 14:24, 0.00s elapsed (1 total hosts)
Overall sending rates: 14705.88 packets / s.
mass_rdns: Using DNS server 127.0.1.1
Initiating Parallel DNS resolution of 1 host. at 14:24
mass_rdns: 0.10s 0/1 [#: 1, OK: 0, NX: 0, DR: 0, SF: 0, TR: 1]
Completed Parallel DNS resolution of 1 host. at 14:24, 0.02s elapsed
DNS resolution of 1 IPs took 0.10s. Mode: Async [#: 1, OK: 0, NX: 1, DR: 0, SF: 0, TR: 1, CN: 0]
Initiating Connect Scan at 14:24
Scanning 192.168.1.9 [1 port]
Discovered open port 445/tcp on 192.168.1.9
Completed Connect Scan at 14:24, 0.00s elapsed (1 total ports)
Overall sending rates: 4716.98 packets / s.
NSE: Script scanning 192.168.1.9.
NSE: Starting runlevel 1 (of 1) scan.
Initiating NSE at 14:24
NSE: Starting smb-vuln-ms17-010 against 192.168.1.9.
NSE: [smb-vuln-ms17-010 192.168.1.9] SMB: Added account '' to account list
NSE: [smb-vuln-ms17-010 192.168.1.9] SMB: Added account 'guest' to account list
NSE: [smb-vuln-ms17-010 192.168.1.9] LM Password:
NSE: [smb-vuln-ms17-010 192.168.1.9] SMB: Invalid NTLM challenge message: unexpected signature.
NSE: [smb-vuln-ms17-010 192.168.1.9] SMB: WARNING: the server appears to be Unix; your mileage may vary.
NSE: [smb-vuln-ms17-010 192.168.1.9] SMB: Extended login to 192.168.1.9 as USER\guest failed, but was given guest access (username may be wrong, or system may only allow guest)
NSE: [smb-vuln-ms17-010 192.168.1.9] Connected to share 'IPC$'
NSE: smb-vuln-ms17-010 against 192.168.1.9 threw an error!
/usr/bin/../share/nmap/scripts/smb-vuln-ms17-010.nse:101: attempt to call field 'pack' (a nil value)
stack traceback:
/usr/bin/../share/nmap/scripts/smb-vuln-ms17-010.nse:101: in function 'check_ms17010'
/usr/bin/../share/nmap/scripts/smb-vuln-ms17-010.nse:177: in function </usr/bin/../share/nmap/scripts/smb-vuln-ms17-010.nse:155>
(...tail calls...)

Completed NSE at 14:24, 0.02s elapsed
Nmap scan report for 192.168.1.9
Host is up, received conn-refused (0.00011s latency).
Scanned at 2017-09-05 14:24:20 IST for 0s
PORT STATE SERVICE REASON
445/tcp open microsoft-ds syn-ack
Final times for host: srtt: 105 rttvar: 3758 to: 100000

NSE: Script Post-scanning.
NSE: Starting runlevel 1 (of 1) scan.
Initiating NSE at 14:24
Completed NSE at 14:24, 0.00s elapsed
Read from /usr/bin/../share/nmap: nmap-payloads nmap-services.
Nmap done: 1 IP address (1 host up) scanned in 0.35 seconds
mrp@user:/usr/share/nmap/scripts$ nmap -version
Nmap version 7.01 ( https://nmap.org )
Platform: x86_64-pc-linux-gnu
Compiled with: liblua-5.2.4 openssl-1.0.2g libpcre-8.38 libpcap-1.7.4 nmap-libdnet-1.12 ipv6
Compiled without:
Available nsock engines: epoll poll select

@tfxrdz
Copy link

tfxrdz commented Oct 31, 2017

i have the same issue

@Sirlsliang
Copy link

Sirlsliang commented Jul 29, 2022 via email

@cldrn
Copy link
Owner

cldrn commented Aug 1, 2022

Are you certain this was a Windows box?

@cldrn cldrn added the Bug label Aug 1, 2022
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