Fix taint tracking out of bounds indexing for extension methods with ref-like parameters #136
Conversation
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
…sion method with a ref-like parameter
Contributor
|
Thanks, I have fixed one more additional case. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Version of #134 against master.
For some reason tests really do not like running on my machine, but... should be fine?
When running taint analysis, calls to extension methods with ref-like (ie. ref or in) parameters can fail with an IndexOutOfRangeException. This is caused by not taking into account the extension methods implicit first parameter.
This PR adds a small test and fixes the issue.
I'm tempted to do a more substantial reworking, but this is feels worth fixing on its own.