New Version for Nessus 6.5 coming soon
October 28th, 2015
A few people have told the parser is not working correctly with latest version of Nessus. I am working determining the issue. Please post a detailed description of that is not working here. Thanks
Categories: Nessus
When will the new version be released that will work with current versions of Nessus? Thanks
I noticed that the “Summary Report Data” is summarizing the top results for each .nessus file and not the aggregated top 0 for all .nessus files. For example, if you have two .nessus files, and both files found the same critical vulnerability, the top 10 critical vulnerabilities would list two entries for the same vulnerability, with the vulnerability count listing the total for each .nessus file.
i’m a big fan of your nessus parser. it’s help me to sort out the result and even used it for a lot of things such as inventory list however i’m facing a problem right now with it.
once i run the script it’s show a message state that there are problem in line 1447. once i opened it i noticed the problem was with Domain controller name. can you help solving the problem please
Hi there. Any update on the new parser for Nessus 6.5 – or to be more accurate, 6.7 ?
Works fine… I’m using strawberry-perl-5.24.0.1-64bit-portable… had to add XML/TreePP and Data/Table with the following commands first:
1. cpan XML::TreePP
2. cpan Data::Table
Then ran the parse_nessus script: perl parse_nessus_xml.v21.pl -f 126.nessus
Hey Cody,
Any update on the new version? 🙂
Hello,
Today I received a nessus file and when launching the parsing, I get :
Creating Spreadsheet Data
Preparing Hosts Data
There is a new plugin family added, it is Incident Response
I’m going to have a look at it to add the new plugin in the parser.
Cheers
The script gets to “Preparing Hosts Data” and then says “There is a new plugin family added, it is Incident Response” and stops.
New update coming today.
new update coming
Coming out today. Next version will be all API based.
Tonight 🙂
Can you better describe the issue?
today
@ddtf9
This was due to a mistake in an update by default the plugin family incident response was activated. I deactivated it from my policies and it worked again.
By the way the parser doesn’t like this plugin in the results.
Is there a new update coming that uses the CVSSv3 information for scoring rather than the CVSSv2 information? Thanks.
I will look into using the CVSS3, but nothing yet.