Ensure that an Array was received in toJniObjectArray()#39
Merged
oleavr merged 1 commit intofrida:masterfrom Aug 8, 2017
leonjza:master
Merged
Ensure that an Array was received in toJniObjectArray()#39oleavr merged 1 commit intofrida:masterfrom leonjza:master
oleavr merged 1 commit intofrida:masterfrom
leonjza:master
Conversation
This allows for a failure to occur earlier instead of later in the call stack when the length property may be needed.
Member
|
Thanks! 💥 |
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.
If a function prototype expects an array, currently, it may be hard to debug this as an exception is thrown relatively deep in the call stack.
To demonstrate this, I set a frida-java playground as detailed here, with the following invalid sample code:
Running this hook, the
registerClass()implementation runs fine, as well as the call to create a$new()one. However, once the hookedinit()implementation is run, the following error occurs:Fixing the hook is a matter of providing and array as expected in the second argument instead of the single
TrustManagerthat is returned from the call to$new().With this check added to ensure that
toJniObjectArray()received an array as expected, the invalid implementation would rather fail earlier, with an error such as: