You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The text was updated successfully, but these errors were encountered:
enovella
changed the title
Possible bug null execution graph when deobfuscating DexProtect'ed strings
Possible bug "null execution graph" when deobfuscating DexProtect'ed strings
Apr 21, 2018
The obvious bug here is the ClassCastException. That's worth looking into.
The problem with the method not getting deobfuscated may be theoretically unsolvable, so really tricky to fix in general. The question for that part is: do you think that method should be optimizable? Are there any obvious loops that rely on file / network IO that may never terminate?
The ClassCastException was caused by the array item being of type Ljava/lang/Object; and APutOp.throwsArrayStoreException() assumes the array item type is always of an "obvious" array type, like "[Ljava/lang/Object;" but this isn't a good assumption. Technically, all arrays, including primitive arrays, are also Ljava/lang/Object;s.
There's no real way to fix the halting problem, which may be the cause of the null graph. Feel free to re-open if you experience an additional bug.
I was messing around with Simplify and
DexProtector
. Tried to deobfuscate strings with:Steps:
Sample (APK):
https://koodous.com/apks/242e0ee59de46c7648b7b38efeb8c088ae3dc8c5c8fe9fbd5e707b098ab8f404
Error:
The text was updated successfully, but these errors were encountered: