-
Notifications
You must be signed in to change notification settings - Fork 82
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
feat: add ASH, Bandit and CDK Nag #530
Conversation
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.
Some initial comments, still WIP
The new Bandit job fails due to 2 occurences of Popen calls with the argument "shell=True" which basically makes the process to be executed via shell. The bandit guideline suggests that the input which is executed in the shell should be properly sanitized / checked to mitigate the risk. @dlpzx How do you want to proceed? Should we simply suppress this warning to get this PR merged, or do you want to have first some input sanitization steps to be implemented, everywhere where this "shell=True" option is used? |
@dbalintx thanks for the input. Agreed - the # nosec comments should be removed and some time should be spent by the team implementing input sanitization for all subprocess calls. semgrep has a guide with mitigation suggestions for example |
@noah-paige @jaidisido, I added some #nosec comments for the shell-true findings. There is a separate issue to track the fix, which has been added to milestone 2.1.0 |
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 - approving this PR
Feature or Bugfix
Detail
Add ASH, Bandit and CDK Nag security checks.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.