Fix parameter handling in FunctionsBuilder - #19520
Merged
Merged
Conversation
Several methods did not explicity label their parameters as unsafe, so it is possible for an application developer to mistakenly supply user controlled data into these parameters creating a SQL injection vector. Thank you to Himanshu Anand for reporting this issue.
markstory
added a commit
that referenced
this pull request
Jul 3, 2026
Fix parameter handling in FunctionsBuilder (#19520) Fix weakness in FunctionsBuilder Several methods did not explicity label their parameters as unsafe, so it is possible for an application developer to mistakenly supply user controlled data into these parameters creating a SQL injection vector. Thank you to Himanshu Anand for reporting this issue. Backport #19520 to 4.x
markstory
added a commit
that referenced
this pull request
Jul 14, 2026
Fix weakness in FunctionsBuilder Several methods did not explicity label their parameters as unsafe, so it is possible for an application developer to mistakenly supply user controlled data into these parameters creating a SQL injection vector. Thank you to Himanshu Anand for reporting this issue.
markstory
added a commit
that referenced
this pull request
Jul 14, 2026
Fix weakness in FunctionsBuilder Several methods did not explicity label their parameters as unsafe, so it is possible for an application developer to mistakenly supply user controlled data into these parameters creating a SQL injection vector. Thank you to Himanshu Anand for reporting this issue.
markstory
added a commit
that referenced
this pull request
Jul 15, 2026
Fix parameter handling in FunctionsBuilder (#19520) Fix weakness in FunctionsBuilder Several methods did not explicity label their parameters as unsafe, so it is possible for an application developer to mistakenly supply user controlled data into these parameters creating a SQL injection vector. Thank you to Himanshu Anand for reporting this issue. Backport #19520 to 4.x
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Several methods did not explicity label their parameters as unsafe, so it is possible for an application developer to mistakenly supply user controlled data into these parameters creating a SQL injection vector.
Thank you to Himanshu Anand for reporting this issue.