A network recon framework published by the CEA (https://github.com/cea-sec) and the ANSSI (https://github.com/ANSSI-FR)
I have a problem with this sample: it has no{"templateID":"CVE-2018-15473","info":{"name":"OpenSSH Username Enumeration","author":["r3dg33k","daffainfo"],"tags":["network","openssh","cve","cve2018"],"description":"OpenSSH through 7.7 is prone to a user enumeration vulnerability due to not delaying bailout for an invalid authenticating user until after the packet containing the request has been fully parsed, related to auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c.","reference":["https://nvd.nist.gov/vuln/detail/cve-2018-15473"],"severity":"medium","classification":{"cve-id":["cve-2018-15473"],"cwe-id":["cwe-362"],"cvss-metrics":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","cvss-score":5.3}},"type":"network","host":"scanme.nmap.org","matched":"scanme.nmap.org:22","timestamp":"2021-10-28T17:16:15.931565-05:00"}
"ip"
field, and the "host"
and "matched"
fields use a hostname, so we cannot know which IP this record is about. If my memory serves well, you (@0xtavian) had the "ip"
field added by the Nuclei team so time ago, it would really be helpful here!
host_timeout
is, as you noted, an option passed to Nmap (so it is based on Nmap's good will). Also, this is a real timeout (in seconds) and it is applied for each host.--nmap-max-cpu
, on the other hand, is a limit applied by the OS (it will kill Nmap if it exceeds it), only based on the CPU usage (if Nmap idles for a very long time, nothing happens), and it is applied for the whole Nmap process (even if it scans 1000 hosts)
ivre runscans*
tools would be great for your use-case, but that depends on your use-case).ivre scan2db
and ivre db2view
).Early httpx (ProjectDiscovery, https://github.com/projectdiscovery/httpx) support in IVRE to be merged soon: ivre/ivre#1262
works great ! Thanks !!!