-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Fixing openvas parser and including script_id for openvas and nmap #11454
base: bugfix
Are you sure you want to change the base?
Conversation
DryRun Security SummaryThe code changes improve the parsing and reporting of security findings from Nmap and OpenVAS tools by enhancing script ID tracking, vulnerability details extraction, and output formatting. Expand for full summarySummary: The provided code changes are focused on improving the parsing and reporting of security findings from two different security tools: Nmap and OpenVAS. The changes to the Nmap parser ( The changes to the OpenVAS XML parser ( Overall, these changes are positive improvements to the application security tooling, as they enhance the ability to track, understand, and report on the identified security findings. The improved parsing and reporting capabilities can benefit security analysts and developers in their efforts to identify and address vulnerabilities within the application. Files Changed:
Code AnalysisWe ran |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Suggestions:
- Check whether we should print
finding.text
whentag == "nvt"
- Move the
test=test
bugfix to a separate PR
i'm including the script_id from tool to consider in the parser of
nmap
andopenvas
fixing a problem of get the id from openvas parser who get the id by the param of the tag.