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

Base64-decoded secrets should not contain strictly ANSI alphanumeric, etc. data #468

Open
michaelcfanning opened this issue May 26, 2021 · 1 comment

Comments

@michaelcfanning
Copy link
Member

This very likely indicates a false positive, eg., we have uncovered a base64-encoded URL that is provided as a query string parameter in an HTTP request (a real world case we encountered).

We should create a helper and call it during the static analysis phase for all relevant rules, returning 'no match' in cases where conditions aren't met (i.e., detecting one or more characters outside the latin unicode range).

@michaelcfanning
Copy link
Member Author

@eddynaka

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

No branches or pull requests

1 participant