Nmap scans are not working
Brought to you by:
greg_k,
mjbrenegan
Menu
▾
▴
#180 Nmap scans are not working
I installed v 1.9.2.014 (from SVN) and nmap scans are not working. Looking at the code, I see the following:
//Insert the job into the database to be scheduled to run
$query="INSERT INTO `nmap_Jobs` ( jobNAME, jobTYPE, jobUSERNAME, methTARGET, methOVERRIDES, restrictSTARTBY, restrictSTARTAFTER, scanNOTIFY, scanSTATE, jobAUTHORIZED, jobAPPROVEDBY, jobSUBMIT ) VALUES
( '$jobNAME', '$jobTYPE', '$jobUSERNAME', '$methTARGET', '$command', now() + INTERVAL 1 day, now(), '$scanNotify', '$scanState', '$jobAuthorized', '$jobAPPROVEDBY', now() ); ";
$result = $dbconn->execute($query);
nmap_Jobs does not exist in the database. I checked all of the SQL install scripts and do not see anything that refers to this table.
Ok, I am in the process of rewriting the nmap stuff. I am starting with a test table nmap_Jobs ( mirror of scan_Jobs ) which the data will ultimately reside in. I have to get the backend code rewritten to do the scanning. I plan to use the scan_Reports and scan_ReportStats and a new table scan_NmapResults to hold the results. This way I can integrate more of the code into a common structure tables, reuse more front-end code.
Also I am working to ensure the bug identified ( commands piped to nmap can not happen ). I did not write the original nmap code and seldomly use it. So me and a teammate are reworking it. I will have the backend code use a targetlist of hosts to scan so no commands can be used to DOS the box in the future, as the nessus code does not have that problem. Our code to prevent sql injection has been very effective. However in this case the cron executing as root accepting a non-validate parameter left a vector of attack. Recommendation is to keep NMAP disabled until I put a build out with a true fix. Likely about another two weeks. I have been very busy.