Cant use nmap output about sicat

[justakazh]

The bug has been fixed, you can update the script and try again

Thanks.

[lay4onok]

The bug has been fixed, you can update the script and try again

Thanks.

Nope. Still i've had the same issue

nmap -sV myIP -oX nmap_out | python .\sicat.py -nm --packetstorm

. ,-'""-._ (,-..,'( |`-/|
-.-' \ )-( , o o)
- \_`"'-
SiCat - The useful exploit finder
@justakazh (https://github.com/justakazh/sicat)

usage : sicat.py --help

usage: sicat.py [-h] [-k KEYWORD] [-kv KEYWORD_VERSION] [-nm NMAP] [--nvd] [--packetstorm] [--exploitdb]
[--exploitalert] [--msfmodule] [-o OUTPUT] [-ot OUTPUT_TYPE]
sicat.py: error: argument -nm/--nmap: expected one argument

[lay4onok]

however it's works in this input properly:

nmap -sV myIP -oX nmap_out | python .\sicat.py -nm nmap_out --nvd

. ,-'""-._ (,-..,'( |`-/|
-.-' \ )-( , o o)
- \_`"'-
SiCat - The useful exploit finder
@justakazh (https://github.com/justakazh/sicat)

usage : sicat.py --help

|

> Starting with Keyword : FortiSSH

|
|- No result in National Vulnearbility Database!
|

> Starting with Keyword : SSL/TLS ClientHello

|

+ National Vulnearbility Database Result
- ID : CVE-2013-0440
- Description : Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 through Update 11, 6 through Update 38, 5.0 through Update 38, and 1.4.2_40 and earlier, and OpenJDK 7, allows remote attackers to affect availability via vectors related to JSSE. NOTE: the previous information is from the February 2013 CPU. Oracle has not commented on claims from another vendor that this issue is related to CPU consumption in the SSL/TLS implementation via a large number of ClientHello packets that are not properly handled by (1) ClientHandshaker.java and (2) ServerHandshaker.java.
- Link : https://nvd.nist.gov/vuln/detail/CVE-2013-0440

|
|
|- Total Result : 7 CVEs Found!
|

> Starting with Keyword : Fortinet security device httpd

|
|- No result in National Vulnearbility Database!

[justakazh]

@lay4onok you can use nmap -sV 1.x.x.x --open -oX nmap_result.xml

thanks

[justakazh]

can i close this issue?

[lay4onok]

It's not me, who opened it, but i think you could