-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Java: CWE-532 sensitive info logging #3090
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
Java: CWE-532 sensitive info logging #3090
Conversation
329ba28
to
d932770
Compare
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.
Thanks for including a query help file with your new query. It makes it much easier for everyone to understand what your query does 😄
I've added a few suggested changes for typos and clarity.
Co-authored-by: Felicity Chapman <felicitymay@github.com>
Co-authored-by: Felicity Chapman <felicitymay@github.com>
…rence so this isn't needed here.
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 inline comments. Also, the ql file needs to be autoformatted to pass PR checks. If you have tested this query on some number of projects it would be nice if you could share a bit of what you learned from looking through the results.
1. Change the regex pattern from variable contains "url" to variable starts with "url" 2. Add the logging trace method to sink
…ther variations are excluded
…ing::localTaintStep(node1, node2)
Third-party logging utilities like Log4J and SLF4J are widely used in Java projects. This PR adds a codeql check for writing sensitive information to debug logs.