Check UTF-8 encoding in JNI functions #5991
Merged
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.
The following JNI functions accept some UTF-8 strings as arguments:
FindClass
GetFieldID
GetMethodID
GetStaticFieldID
GetStaticMethodID
RegisterNatives
This patch checks that the UTF-8 strings provided to these methods are correctly encoded. If they are not, then the proper JNI error reporting behavior is performed, mainly:
FindClass
throwsNoClassDefFoundError
.GetFieldID
andGetStaticFieldID
throwNoSuchFieldError
.GetMethodID
,GetStaticMethodID
andRegisterNatives
throwNoSuchMethodError
.