-
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
🐛 fix hcl_appscan, handle severity is None #10074 #10101
Conversation
Hi there 👋, @DryRunSecurity here, below is a summary of our analysis and findings.
Note 🟢 Risk threshold not exceeded. Change Summary (click to expand)The following is a summary of changes in this pull request made by me, your security buddy 🤖. Summary: The changes in this pull request focus on improving the quality and reliability of the HCL AppScan parser, which is an essential component for effectively integrating application security scanning into the development process. The key changes include:
While the changes appear to be focused on improving the parser's functionality, it's important to ensure that the parsing process is robust and secure, as vulnerabilities in the parser could potentially lead to security issues in the overall application security monitoring and reporting process. Files Changed:
Powered by DryRun Security |
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.
Approved
Approved before tests finished running... will give it a moment to complete
see #10074
However, the scanfile was not very helpful as a lot of values were rotated (e.g. also severity and cwe) and I had to rotate those back to get something useful.
I figured out that some severity values were None and fixed it with the scan file.