Skip to content
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

Fixed #42: Non-system exec calls incorrectly flagged. #43

Merged
merged 1 commit into from
Aug 4, 2019

Conversation

danepowell
Copy link
Contributor

Fixes #42

I see that a very similar issue was previously fixed for another sniff: #20

It seems like this is a pretty common pattern that should be fixed comprehensively somehow. But this PR at least solves it for my use case.

@jmarcil
Copy link
Collaborator

jmarcil commented Aug 4, 2019

Hello @danepowell,

thank you for your contribution.

I agree that this concern is more broad than just for this function call. This was actually tracked as issue #31 after receiving #20.

I've looked around to see if there's any impact on your change on getSystemexecFunctions and it looks like we can suppress findings even in paranoia mode. I'll merge it!

Thanks again!

@jmarcil jmarcil merged commit 510be5c into FloeDesignTechnologies:master Aug 4, 2019
@danepowell
Copy link
Contributor Author

Thank you for reviewing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

BadFunctions.SystemExecFunctions incorrectly flags non-system exec function calls
2 participants