You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ ./ssh-auditor addcredential root root
$ ./ssh-auditor addcredential admin admin
$ ./ssh-auditor addcredential guest guest --scan-interval 1 #check this once per day
Try credentials against discovered hosts
$ ./ssh-auditor scan
Output a report on what credentials worked
$ ./ssh-auditor vuln
RE-Check credentials that worked
$ ./ssh-auditor rescan
Output a report on duplicate key usage
$ ./ssh-auditor dupes
TODO
update the 'host changes' table
handle false positives from devices that don't use ssh password authentication but instead use the shell to do it.
variable re-check times - each credential has a scan_interval in days
better support non-standard ports - discover is the only thing that needs to be updated, the rest doesn't care.
possibly daemonize and add an api that bro could hook into to kick off a discover as soon as a new SSH server is detected.
make the store pluggable (mysql, postgresql).
differentiate between a failed password attempt and a failed connection or timeout. Mostly done. Things like fail2ban complicate this.
add go implementations for the report sqlite3 command.
Report query.
This query that ssh-auditor vuln runs is
select
hc.hostport, hc.user, hc.password, hc.result, hc.last_tested, h.version
from
host_creds hc, hosts h
where
h.hostport = hc.hostport
and result!='' order by last_tested asc
About
The best way to scan for weak ssh passwords on your network