.nessus file import

kab00kie · January 18, 2016, 4:40pm

When I upload a .nessus in Dradis 3.0 there is no output and it’s added as an Uploaded file - that’s all.

Any help? I did have an issue with Nmap files but found the fix here but for Nessus I am not receiving any errors or output at all.

Thanks

kab00kie · January 18, 2016, 5:57pm

Just some more info from production.log that I haven’t looked into the solution for yet:

I, [2016-01-18T12:52:34.635676 #2331] INFO – : Parameters: {“item_id”=>“3”, “uploader”=>“Dradis::Plugins::Nessus”, “file”=>“File.nessus”}
I, [2016-01-18T12:52:34.645969 #2331] INFO – : Completed 500 Internal Server Error in 10ms
F, [2016-01-18T12:52:34.654196 #2331] FATAL – :
Redis::CannotConnectError (Error connecting to Redis on 127.0.0.1:6379 (Errno::ECONNREFUSED)):

kab00kie · January 18, 2016, 6:20pm

Hope this isn’t considered spam, sorry if so.

Changed the port config in the Redis config (/etc/redis/redis.conf) from 0 to 6379.

.nessus file upload now says it’s Queuing a job to start in the background but nothing yet. Waiting patiently.

kab00kie · January 18, 2016, 6:56pm

Looks like enough restarts of Dradis will sometimes fix this problem.

Found a bit of info here: Redirecting to Google Groups

etd · January 27, 2016, 9:55am

Another cause could be if the background worker process (the one that picks jobs from the Redis queue) is not working.

If you run ps aux | grep resque do you see something like this?

$ ps aux | grep resq
etd             81627   0.0  1.1  2576004  90100 s003  S+    2:05pm   0:24.58 resque-1.25.2: Waiting for *

Alternatively you can upload project directly using Thor with:

$ RAILS_ENV=production bundle exec thor dradis:plugins:nessus:upload /path/to/nessus

HTH,
Daniel

zwebel · January 29, 2016, 9:04pm

Hi kab00kie

I tried to follow these steps:
In order to rule out anything weird the file processing, I’d recommend
you process the file “by hand”:

$ cd /usr/local/rails/dradispro/current

edit the ./vendor/plugins/nessus_upload/lib/tasks/thorfile.rb and just
before the NessusUpload::import() in line #17 add:

Node.set_set_project_scope( 12 )
Note.set_set_project_scope( 12 )

But I could not find the correct thorfile because I use the community edition.
could you please put me in the right direction for the community edition?

Thanks.

zwebel · January 29, 2016, 9:08pm

Hi Daniel,

I tried to upload the nessus result directly without any luck.
Here the result:

kali2:/opt/dradis/dradisframework# RAILS_ENV=production bundle exec thor dradis:plugins:nessus:upload /root/host/LSV21-IRP3_r00ii3.nessus
Faraday::Builder is now Faraday::RackBuilder.
Loaded add-ons:
acunetix - Processes Acunetix XML format
burp - Processes Burp Scanner XML output
csv - Export results in comma-separated values
html_export - Generate advanced HTML reports
mediawiki - Import entries from an external MediaWiki
nessus - Processes Nessus XML v2 format (.nessus)
nexpose - Processes Nexpose XML format
nikto - Processes Nikto output
nmap - Processes Nmap output
nto_spider - Processes NTOSpider reports
open_vas - Processes OpenVAS XML v6 or v7 format
pdf_export - Generate PDF reports
qualys - Processes Qualys output
snowcrash - This plugin doesn’t provide a :description
vulndb - Import entries from your VulnDB HQ repository
I, [2016-01-29T21:42:40.920483 #6938] INFO – : Parsing nessus output file…
I, [2016-01-29T21:42:41.220303 #6938] INFO – : Done.
I, [2016-01-29T21:42:41.222986 #6938] INFO – : Processing report: LSV21-IRP3
/usr/lib/ruby/vendor_ruby/sqlite3/database.rb:91:in initialize': SQLite3::SQLException: no such table: dradis_nodes: SELECT "dradis_nodes".* FROM "dradis_nodes" WHERE "dradis_nodes"."label" = 'plugin.output' LIMIT 1 (ActiveRecord::StatementInvalid) from /usr/lib/ruby/vendor_ruby/sqlite3/database.rb:91:in new’
from /usr/lib/ruby/vendor_ruby/sqlite3/database.rb:91:in prepare' from /var/lib/gems/2.1.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/sqlite3_adapter.rb:301:in block in exec_query’
from /var/lib/gems/2.1.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract_adapter.rb:373:in block in log' from /var/lib/gems/2.1.0/gems/activesupport-4.1.9/lib/active_support/notifications/instrumenter.rb:20:in instrument’
from /var/lib/gems/2.1.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract_adapter.rb:367:in log' from /var/lib/gems/2.1.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/sqlite3_adapter.rb:298:in exec_query’
from /var/lib/gems/2.1.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/sqlite3_adapter.rb:510:in select' from /var/lib/gems/2.1.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/database_statements.rb:24:in select_all’
from /var/lib/gems/2.1.0/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/query_cache.rb:70:in select_all' from /var/lib/gems/2.1.0/gems/activerecord-4.1.9/lib/active_record/querying.rb:39:in find_by_sql’
from /var/lib/gems/2.1.0/gems/activerecord-4.1.9/lib/active_record/relation.rb:611:in exec_queries' from /var/lib/gems/2.1.0/gems/activerecord-4.1.9/lib/active_record/relation.rb:493:in load’
from /var/lib/gems/2.1.0/gems/activerecord-4.1.9/lib/active_record/relation.rb:238:in to_a' from /var/lib/gems/2.1.0/gems/activerecord-4.1.9/lib/active_record/relation/finder_methods.rb:460:in find_take’
from /var/lib/gems/2.1.0/gems/activerecord-4.1.9/lib/active_record/relation/finder_methods.rb:98:in take' from /var/lib/gems/2.1.0/gems/activerecord-4.1.9/lib/active_record/relation/finder_methods.rb:81:in find_by’
from /var/lib/gems/2.1.0/gems/activerecord-4.1.9/lib/active_record/relation.rb:209:in find_or_create_by' from /var/lib/gems/2.1.0/gems/activerecord-4.1.9/lib/active_record/querying.rb:6:in find_or_create_by’
from /opt/dradis/dradis-plugins/lib/dradis/plugins/content_service.rb:168:in default_parent_node' from /opt/dradis/dradis-plugins/lib/dradis/plugins/content_service.rb:65:in create_node’
from /opt/dradis/dradis-nessus/lib/dradis/plugins/nessus/importer.rb:39:in block (2 levels) in import' from /var/lib/gems/2.1.0/gems/nokogiri-1.6.5/lib/nokogiri/xml/node_set.rb:237:in block in each’
from /var/lib/gems/2.1.0/gems/nokogiri-1.6.5/lib/nokogiri/xml/node_set.rb:236:in upto' from /var/lib/gems/2.1.0/gems/nokogiri-1.6.5/lib/nokogiri/xml/node_set.rb:236:in each’
from /opt/dradis/dradis-nessus/lib/dradis/plugins/nessus/importer.rb:35:in block in import' from /var/lib/gems/2.1.0/gems/nokogiri-1.6.5/lib/nokogiri/xml/node_set.rb:237:in block in each’
from /var/lib/gems/2.1.0/gems/nokogiri-1.6.5/lib/nokogiri/xml/node_set.rb:236:in upto' from /var/lib/gems/2.1.0/gems/nokogiri-1.6.5/lib/nokogiri/xml/node_set.rb:236:in each’
from /opt/dradis/dradis-nessus/lib/dradis/plugins/nessus/importer.rb:26:in import' from /opt/dradis/dradis-nessus/lib/tasks/thorfile.rb:36:in upload’
from /usr/lib/ruby/vendor_ruby/thor/command.rb:27:in run' from /usr/lib/ruby/vendor_ruby/thor/invocation.rb:126:in invoke_command’
from /usr/lib/ruby/vendor_ruby/thor.rb:359:in dispatch' from /usr/lib/ruby/vendor_ruby/thor/base.rb:440:in start’
from /usr/lib/ruby/vendor_ruby/thor/runner.rb:36:in method_missing' from /usr/lib/ruby/vendor_ruby/thor/command.rb:29:in run’
from /usr/lib/ruby/vendor_ruby/thor/command.rb:126:in run' from /usr/lib/ruby/vendor_ruby/thor/invocation.rb:126:in invoke_command’
from /usr/lib/ruby/vendor_ruby/thor.rb:359:in dispatch' from /usr/lib/ruby/vendor_ruby/thor/base.rb:440:in start’
from /usr/bin/thor:6:in `’
kali2:/opt/dradis/dradisframework#

I hope this gives a hint.

Robiin · February 26, 2016, 1:44pm

Hi Daniel,

I did the manual Nessus file upload which succeeded however the upload through the web portal gives me the same error as Kab00kie has. When I tried out the packaged Dradis I was able to start a worker thread, but how can I do this with the GIT install?

etd · March 2, 2016, 7:26pm

@Robiin, as explained in the How do I run it? section of the Download page, when you get the package you run two scripts:

$ ./dradis-webapp  && ./dradis-worker

In order for this to work, you need Redis installed in the system.

The key line in the dradis-worker script is:

github.com

dradis/dradis-legacy/blob/master/packaging/dradis-worker#L19


      
          . lib/wrapper-common.sh
          
          
# Check if Redis is running
          redis-cli ping > /dev/null 2>&1 || { printf "Could not connect to Redis.\nPlease make sure Redis is installed and running and try again.\n"; exit 1; }
          
          
# Avoid resque deprecation Warning
          # http://hone.herokuapp.com/resque/2012/08/21/resque-signals.html
          export TERM_CHILD=1
          
          
printf "Starting resque worker in the background...\n"
          exec "$SELFDIR/lib/ruby/bin/ruby" -rbundler/setup "$SELFDIR/lib/app/bin/rake" resque:work $* &

which you can duplicate by running the following in a new terminal window:

$ RAILS_ENV=production bundle exec rake resque:work

We’re looking into ways of making this ‘start’ process more user friendly though…

HTH

Robiin · March 7, 2016, 9:05am

etd:

In order for this to work, you need Redis installed in the system.

The key line in the dradis-worker script is:

https://github.com/dradis/dradisframework/blob/master/packaging/dradis-worker#L19

which you can duplicate by running the following in a new terminal window:
$ RAILS_ENV=production bundle exec rake resque:work

This worked great, thank you!

danielm · February 14, 2017, 2:35pm

I replicated the steps you mentioned:

make redis listen on port 127.0.0.1:6379
restarted the redis server
start worker with: RAILS_ENV=production bundle exec rake resque:work
started dradis

Still, all I get is the “Enqueueing job to start…” message and no results.
I am using the community edition.
So why is dradis not parsing the file?

rachkor · February 14, 2017, 6:48pm

@danielm this thread is ~1 year old. Have you followed the install steps in this guide? Installing Dradis from Git | Dradis Framework (#5 under “Setting up the app”) I’m wondering whether starting the worker with $ bundle exec rake resque:work instead would do the trick as dradis-ce runs in development by default.

danielm · February 17, 2017, 2:25pm

Thank you for your reply. I have acquired a pro license and surmise that the problem will vanish.

Topic		Replies	Views
.nessus import not working on Kali Community Edition	11	1695	November 9, 2018
Python request to post a file to Upload manager? Community Edition	5	778	February 17, 2021
Issues with uploads	3	2732	June 28, 2016
Upload nmap xml doesn't work Community Edition	1	1309	March 7, 2017
Metasploit module work's not fine( Community Edition	1	1109	March 2, 2018

.nessus file import

Related Topics