-
Notifications
You must be signed in to change notification settings - Fork 18
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
OpenVAS parsing #18
Comments
@Drunkenslav can you add a full xml example? |
It's thousands of lines so i pasted it here: https://pastebin.pl/view/60aea84e Version of OpenaVAS GMP is the newest one: 21.4 |
btw I dont want to ask too much but OpenVAS does not work with Critical severity (max is High). If it would be possible to parse CVSS 9.0 and above as Critical, that would be jjust awesome. But if not, its fine :) |
Hello any update on this please? Or can specify which version of OpenVas you use so i can use that meanwhile? Thank you! |
@Drunkenslav the "critical severity" issue will be on the next plugins release. The CVE link, that will be in the v4 of the UI (the CVE on the manage will be a link to que CVE description) |
Awesome, thanks |
@Drunkenslav faraday-plugins 1.6.5 is out. |
Hello,
first off, great job on this project. I love it! I would just like a bit more information from OpenVAS XML to be parsed.
What's the problem this feature will solve?
Will help with user effectivity
Describe the solution you'd like
If more information would be parsed it would be great. Usually for each finding Openavas adds references and CVE (if applicable)
OpenVAS XML:
CVE's after being parsed could be hyperlinked - https://cve.mitre.org/cgi-bin/cvename.cgi?name=$CVENUM
The current parsing does give you only description and solution, but if you need more information, you need to google. But OpenVAS XML gives you nice references, so you would just click the link to get more information without wasting valuable time :)
Thanks
The text was updated successfully, but these errors were encountered: