[K9VULN-10631] Add taint propagation within return expression#800
Merged
jasonforal merged 1 commit intomainfrom Jan 7, 2026
Merged
[K9VULN-10631] Add taint propagation within return expression#800jasonforal merged 1 commit intomainfrom
jasonforal merged 1 commit intomainfrom
Conversation
juli1
approved these changes
Jan 7, 2026
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
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.
What problem are you trying to solve?
Currently, the data flow implementation doesn't properly draw graph edges from the expression of a return statement. For example, in the following, the two references of
userInputaren't connected (but should be):What is your solution?
Visit the
return_statementbut don't propagate from it.Alternatives considered
N/A
What the reviewer should know
N/A