Hi,
A few weeks back I submitted a post
regarding that Nessus can not
find MySQL. I wanted to test Nessus against hosts running non-
standard ports. I set up MySQL to listen on port 5506. I found that
Nessus does not recognized MySQL on that port. In fact, it doesn't
report anything, except that the port is open.
Since my post, I noticed a couple
of things. First, after reviewing the
nessusd.messages file, I found that Nessus is killing the
find_services plugin because its too slow. I've increased the timeout
up to 60 second and Nessus still kills it. So my first assumption is
that the find_service plugin is killed before it can evaluate port 5506.
Could this be the case?
I decided to run Nmap separately,
alter the results so that only port
5506 is listed, feed Nessus the Nmap results, and run Nessus. This
time, nessus did not kill the find_services plugin, but it still did not
report anything for port 5506. I thought, at least, it should report the
banner, right?
Nex,t I decided to look at the source
for find_service and noticed that
its looking the mysql banner as "hhost " or "whost " on the first line
and "mysql" on the second. However, If I run telnet on the mysql
port (5506) I found that the banner is: 9
4.0.8-gamma-standard-logG\{v^Th2
For kicks, I changed the find_service
code to check for this banner.
Sure enough, it works if I feed Nessus with one port (5506) from my
Nmap scan. Although it doesn't work when I run a Nmap scan of all
ports. Go figure.
I' m running Nessus 1.2.7 on RedHat
8.0. The host that I am
primarily testing is Red Hat 8.0 with MySQL version 4.0.8. I have
same issues with other hosts running Red Hat 7.1 and MySQL
3.23.51
Has anyone had any similar occurrences,
particularly, with
find_services not completing?
Thank you in advance,
Neal Dawson
[EMAIL PROTECTED]
