Foxhound: only create TaintOperation for tainted strings#206
Closed
tmbrbr wants to merge 1 commit into
Closed
Conversation
tmbrbr
commented
Mar 15, 2024
| if(newtaint.hasTaint()) { | ||
| newtaint.extend(op); | ||
| if (newtaint.hasTaint()) { | ||
| newtaint.extend(TaintOperationFromContext(cx, "unescape", true, str)); |
Contributor
Author
There was a problem hiding this comment.
This could cause GC problems - if TaintOperationFromContext needs to allocate memory (e.g. by flattening str), then result might be freed as it is not rooted!
Contributor
Author
There was a problem hiding this comment.
Could probably mitigate this by moving it up before Step 6
Collaborator
|
Superseeded by #336. |
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.
Some more optimization, this time for unescape operations.