taint-config files java-lang.txt and scala.txt propagate taint from character types #712
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.
For Issue#711 the taint on StringBuilder and StringBuffer from character types is propagated, and Character class is no longer considered SAFE.
Because libraries may turn strings into character arrays and then rebuild the string, we cannot assume that adding characters individually to a string will be untainted.
This pull request changes the taint configuration for both the java-lang and scala classes that deal with individual characters.