-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parsing errors? #12
Comments
any update here? |
any update? |
I guess it's a bit late but... For some reason, in your Other than that, both Nessus plugins has the same Output. |
@xkillbit I checked your attachment, it's not reported as
Risk Factor in your case is <ReportItem port="80" svc_name="www" protocol="tcp" severity="3" pluginID="34460" pluginName="Unsupported Web Server Detection" pluginFamily="Web Servers">
<cvss3_base_score>10.0</cvss3_base_score>
<cvss_base_score>7.5</cvss_base_score>
<risk_factor>High</risk_factor> I assume Nessus takes into account
What value do you have set in Nessus for @lapolis thanks for the input. |
Hello,
Here is the CLI tool count followed by a script that dumps each Vuln Name by criticality and provides a count. Notice the counts are not the same. In this example, lets focus on just the Criticals:
Nessus web interface for comparison:
As you can see by comparing, the parser does not account for "Unsupported Web Server Detection".
I've attached the dummy data from the scan against the HTB environment, followed by the script used to dump and count each vuln by severity.
dummy_data.zip
I would appreciate any help.
The text was updated successfully, but these errors were encountered: