Nessus send no data to seccubus #603
Comments
This is the log output: Scan export status request returned 404Server returned error: The requested file was not found $VAR1 = { Note: seccubus installed from RPM on Fedora 26 |
Things that might help:
|
note: locally reproducing this error failed on CentOS7; everything works here despite the fight of installing Mojolicious on CentOS7. I'll get their output soon and see what their issue is. |
a scan run an finished via nessus without problmes .. after the scan is finish i get the error like @Ar0xA |
Does the scan actually return findings? Is a run created in the runs tab?
Sent with big fingers from a small keyboard, don't blame me for typios please...
…________________________________
From: womanizzzer <notifications@github.com>
Sent: Saturday, November 11, 2017 4:37:50 PM
To: schubergphilis/Seccubus
Cc: Frank Breedijk; Mention
Subject: Re: [schubergphilis/Seccubus] Nessus send no data to seccubus (#603)
a scan run an finished via nessus without problmes .. after the scan is finish i get the error like @Ar0xA<https://github.com/ar0xa>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#603 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABA5bn_Hl5sy3KZAfvnSl_3NRkOU3miJks5s1b9OgaJpZM4QXn5H>.
|
Would it be possible to contact me directly so I can look at things on your system? @Ar0xA has my details. |
The Scan doesnt return findings and doesnt created in runs tab. |
I should be available all day Wednesday. Seccubus is designed not to import a scan when it contains no fidnigns at all, because it assumes that this is due to a scanner failure. So if yuor Nessus job does not have any findings at all it will not be imported. We are running a setup here that launches about 40 nessus jobs each month. I'm having a hard time replicating your issue so would like to look into your system a bit to see if we can find a root cause. |
I will have a look at it soon at one of my colleague's systems, but thats unlikely today due to other work. I have more information though: it seems everything goes fine, until the scan is finished and Seccubus tries to retrieve the data itself (-v -v -v output)
Note the Nessus 500 error |
My Nessus Scanner list me a lot of findings ... |
in attachment my seccubus output with -v -v -v and two pictures from my nessus scanner as proof |
@womanizzzer unfortunately, you text gto truncated, but here's what I've been able to find out.
The text stops in the middle of the HTML report. Couple of things to try:
|
@seccubus first time information about nessus version. |
In my (successful) test I used the trial Pro version. One colleague also used Home and the other tried the trial of Pro. I have a session in a few minutes in which I'll spend some time seeing if I can debug this, on their systems. Will update once I have more information. |
now i add parameters --export nessus --export html to scan and it works. |
I verified with my colleague, from the Nessus webinterface, he also has no "Export" to PDF option. Which would explain why this fails. I will check to see if i can find out why Nessus cant export to PDF |
@seccubus suggested fix from my side would be to have Seccubus by default export to .nessus or .html format instead of pdf |
The PDF is important to some users dropping it by default seems to be a bad idea (tm). I need to find out if I can find out if a pdf report is available. Also I should fail gently in stead of critically. |
ah ok, yeah. Since Nessus gives a 500 error when the export fails, how about after an error 500 then automatically try .html instead? And indeed, some kind of logging "export to [format] failed" in -v -v -v format would help debugging this in the future. edit: checking the Nessus 6 API, I do not see a call to check what export formats Nessus supports :( |
Currently the |
@seccubus Seccubus start scans on nessus, but seccubus receives no results from nessus.
I tried scans internal and external, both variant dont work
The text was updated successfully, but these errors were encountered: