configtest and scan Failed

[shigechika]

What did you do? (required. The issue will be closed when not provided.)

vuls configtest
vuls scan

What did you expect to happen?

works fine

What happened instead?

ERROR

• Current Output

$ vuls configtest
[Feb 14 14:16:34]  INFO [localhost] vuls-v0.19.3-build-20220214_115853_0733561
[Feb 14 14:16:34]  INFO [localhost] Validating config...
[Feb 14 14:16:34]  INFO [localhost] Detecting Server/Container OS...
[Feb 14 14:16:34]  INFO [localhost] Detecting OS of servers...
[Feb 14 14:16:35] ERROR [localhost] (1/150) Failed: example1, err: [Failed to print SSH configuration. err:
    github.com/future-architect/vuls/scanner.validateSSHConfig
        /home/vuls/go/src/github.com/future-architect/vuls/scanner/serverapi.go:368
  - exit status 255]
[Feb 14 14:16:35] ERROR [localhost] (2/150) Failed: example2, err: [Failed to name resolution. Please check the HostName settings for SSH:
    github.com/future-architect/vuls/scanner.validateSSHConfig
        /home/vuls/go/src/github.com/future-architect/vuls/scanner/serverapi.go:385]
[Feb 14 14:16:35] ERROR [localhost] (3/150) Failed: example3, err: [Failed to name resolution. Please check the HostName settings for SSH:
    github.com/future-architect/vuls/scanner.validateSSHConfig
        /home/vuls/go/src/github.com/future-architect/vuls/scanner/serverapi.go:385]
 : snip

Please re-run the command using -debug and provide the output below.

Steps to reproduce the behaviour

Configuration (MUST fill this out):

• Go version (go version):

go version go1.16.3 linux/amd64

• Go environment (go env):

• Vuls environment:

Hash : ____

To check the commit hash of HEAD
$ vuls -v
vuls-v0.19.3-build-20220214_115853_0733561

or

$ cd $GOPATH/src/github.com/future-architect/vuls
$ git rev-parse --short HEAD
0733561

• config.toml:

[default]
port = "22"
user = "vuls"
keyPath = "/home/vuls/.ssh/id_rsa"
sshConfigPath = "/home/vuls/.ssh/config"

[servers.example1]
host = "example1.example.jp"

[servers.example2]
host = "example2.example.jp"

[servers.example3]
host = "example3.example.jp"

• command:

[MaineK00n]

In the following environment, configtest and scan are running.

$ vuls configtest
[Feb 15 04:17:10]  INFO [localhost] vuls-v0.19.3-build-20220215_041110_0733561
[Feb 15 04:17:10]  INFO [localhost] Validating config...
[Feb 15 04:17:10]  INFO [localhost] Detecting Server/Container OS... 
[Feb 15 04:17:10]  INFO [localhost] Detecting OS of servers... 
[Feb 15 04:17:11]  INFO [localhost] (1/1) Detected: vuls-target: debian 11.2
[Feb 15 04:17:11]  INFO [localhost] Detecting OS of containers... 
[Feb 15 04:17:11]  INFO [localhost] Checking Scan Modes...
[Feb 15 04:17:11]  INFO [localhost] Checking dependencies...
[Feb 15 04:17:11]  INFO [vuls-target] Dependencies... Pass
[Feb 15 04:17:11]  INFO [localhost] Checking sudo settings...
[Feb 15 04:17:11]  INFO [vuls-target] sudo ... No need
[Feb 15 04:17:11]  INFO [localhost] It can be scanned with fast scan mode even if warn or err messages are displayed due to lack of dependent packages or sudo settings in fast-root or deep scan mode
[Feb 15 04:17:11]  INFO [localhost] Scannable servers are below...
vuls-target

$ vuls scan
[Feb 15 04:17:35]  INFO [localhost] vuls-v0.19.3-build-20220215_041110_0733561
[Feb 15 04:17:35]  INFO [localhost] Start scanning
[Feb 15 04:17:35]  INFO [localhost] config: /home/mainek00n/github/github.com/MaineK00n/vuls/config.toml
[Feb 15 04:17:35]  INFO [localhost] Validating config...
[Feb 15 04:17:35]  INFO [localhost] Detecting Server/Container OS... 
[Feb 15 04:17:35]  INFO [localhost] Detecting OS of servers... 
[Feb 15 04:17:36]  INFO [localhost] (1/1) Detected: vuls-target: debian 11.2
[Feb 15 04:17:36]  INFO [localhost] Detecting OS of containers... 
[Feb 15 04:17:36]  INFO [localhost] Checking Scan Modes... 
[Feb 15 04:17:36]  INFO [localhost] Detecting Platforms... 
[Feb 15 04:17:37]  INFO [localhost] (1/1) vuls-target is running on other
[Feb 15 04:17:37]  INFO [vuls-target] Scanning OS pkg in fast mode
[Feb 15 04:17:38]  WARN [vuls-target] kernel running version is invalid. skip kernel vulnerability detection. actual kernel version: Jan, err: upstream_version must start with digit
[Feb 15 04:17:38]  INFO [vuls-target] Scanning listen port...
[Feb 15 04:17:38]  INFO [vuls-target] Using Port Scanner: Vuls built-in Scanner


Scan Summary
================
vuls-target	debian11.2	319 installed





To view the detail, vuls tui is useful.
To send a report, run vuls report -h.

• config.toml

[default]
port               = "2222"
user               = "root"
keyPath            = "/home/mainek00n/github/github.com/MaineK00n/vuls-targets-docker/.ssh/id_rsa"
sshConfigPath	   = "/home/mainek00n/.ssh/config"

[servers]
[servers.vuls-target]
host = "vuls-target"
# host = "127.0.0.1"

• /home/mainek00n/.ssh/config

Host vuls-target
    HostName 127.0.0.1
    Port 2222
    Identityfile ~/github/github.com/MaineK00n/vuls-targets-docker/.ssh/id_rsa
    Identitiesonly yes
    User root
    KexAlgorithms +diffie-hellman-group1-sha1

[MaineK00n]

If using the information in ssh_config, configtest and scan will work even if config.toml is written like this.
By using $ ssh -G, the config information at the time of ssh can be found.
From there, hostname, user, and port can be found.
The hostname is used to check if the name can be resolved.
From the hostname, user, and port, we can check if they are registered in known_hosts.

$ vuls configtest -debug
[Feb 15 04:26:36]  INFO [localhost] vuls-v0.19.3-build-20220215_041110_0733561
[Feb 15 04:26:36]  INFO [localhost] Validating config...
[Feb 15 04:26:36]  INFO [localhost] Detecting Server/Container OS... 
[Feb 15 04:26:36]  INFO [localhost] Detecting OS of servers... 
[Feb 15 04:26:36] DEBUG [localhost] Validating SSH Settings for Server:vuls-target ...
[Feb 15 04:26:36] DEBUG [localhost] Executing... /usr/bin/ssh -G -F /home/mainek00n/.ssh/config vuls-target
[Feb 15 04:26:36] DEBUG [localhost] Setting SSH User:root for Server:vuls-target ...
[Feb 15 04:26:36] DEBUG [localhost] Validating SSH HostName:127.0.0.1 for Server:vuls-target ...
[Feb 15 04:26:36] DEBUG [localhost] Setting SSH Port:2222 for Server:vuls-target ...
[Feb 15 04:26:36] DEBUG [localhost] Checking if the host's public key is in known_hosts...
[Feb 15 04:26:36] DEBUG [localhost] Executing... /usr/bin/ssh-keygen -F "[127.0.0.1]:2222" -f ~/.ssh/known_hosts
...
[Feb 15 04:26:37]  INFO [localhost] Scannable servers are below...
vuls-target

• config.toml

[default]
sshConfigPath	   = "/home/mainek00n/.ssh/config"

[servers]
[servers.vuls-target]
host = "vuls-target"

• /home/mainek00n/.ssh/config

Host vuls-target
    HostName 127.0.0.1
    Port 2222
    Identityfile ~/github/github.com/MaineK00n/vuls-targets-docker/.ssh/id_rsa
    Identitiesonly yes
    User root
    KexAlgorithms +diffie-hellman-group1-sha1

[shigechika]

$ ping direct
ping: cannot resolve direct: Unknown host

$ ping -c 1 direct.example.jp
PING direct.example.jp (192.168.0.10): 56 data bytes
64 bytes from 192.168.0.10: icmp_seq=0 ttl=61 time=1.840 ms

--- direct.example.jp ping statistics ---
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.840/1.840/1.840/0.000 ms

$ vuls-v0.19.3-build-20220214_115853_0733561 configtest -debug direct
[Feb 15 13:15:23]  INFO [localhost] vuls-v0.19.3-build-20220214_115853_0733561
[Feb 15 13:15:23]  INFO [localhost] Validating config...
[Feb 15 13:15:23]  INFO [localhost] Detecting Server/Container OS...
[Feb 15 13:15:23]  INFO [localhost] Detecting OS of servers...
[Feb 15 13:15:23] DEBUG [localhost] Validating SSH Settings for Server:direct ...
[Feb 15 13:15:23] DEBUG [localhost] Executing... /bin/ssh -G -F /home/vuls/.ssh/config -p 22 -l vuls direct.example.jp
[Feb 15 13:15:23] DEBUG [localhost] Setting SSH User:vuls for Server:direct ...
[Feb 15 13:15:23] DEBUG [localhost] Validating SSH HostName:direct.example.jp for Server:direct ...
[Feb 15 13:15:23] DEBUG [localhost] Setting SSH Port:22 for Server:direct ...
[Feb 15 13:15:23] DEBUG [localhost] Checking if the host's public key is in known_hosts...
[Feb 15 13:15:23] DEBUG [localhost] Executing... /bin/ssh-keygen -F direct.example.jp -f /dev/null
[Feb 15 13:15:23] DEBUG [localhost] Executing... /bin/ssh-keygen -F direct.example.jp -f /etc/ssh/ssh_known_hosts
[Feb 15 13:15:23] DEBUG [localhost] Executing... /bin/ssh-keygen -F direct.example.jp -f /etc/ssh/ssh_known_hosts2
[Feb 15 13:15:23] ERROR [localhost] (1/1) Failed: direct, err: [Failed to find the host in known_hosts. Plaese exec `$ ssh -F /home/vuls/.ssh/config -i /home/vuls/.ssh/id_rsa -p 22 -l vuls direct.example.jp` or `$ ssh-keyscan -H -p 22 direct.example.jp >> /dev/null`:
    github.com/future-architect/vuls/scanner.validateSSHConfig
        /home/vuls/go/src/github.com/future-architect/vuls/scanner/serverapi.go:449]
[Feb 15 13:15:23] ERROR [localhost] Failed to configtest: Failed to init servers. err:
    github.com/future-architect/vuls/scanner.Scanner.Configtest
        /home/vuls/go/src/github.com/future-architect/vuls/scanner/serverapi.go:116
  - No scannable host OS:
    github.com/future-architect/vuls/scanner.Scanner.initServers
        /home/vuls/go/src/github.com/future-architect/vuls/scanner/serverapi.go:252

• config.toml

[default]
keyPath="/home/vuls/.ssh/id_rsa"

[server.direct]
host="direct.example.jp"

• .ssh/config
  Nothing

[shigechika]

works fine. looks good😀