update to rails unsafe reflection methods #3265
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
👋 Hey team!
I believe I've identified a false positive here.
This rule was intended to match when user input was provided as an argument to the
.tap
method. Here's the relevant brakeman rule that this was related to: https://github.com/presidentbeef/brakeman/blob/main/lib/brakeman/checks/check_unsafe_reflection_methods.rbWhat I found in practice was that this would match whenever object the
.tap
method was called ON as well. I ran into this with a bit of code that looked like thisIn this case, the user input is not being passed in to the
tap
method, so I'm pretty sure there's no risk of unsafe reflection? I couldn't think of a way at least 🙃