Common problems that i faced in android pentesting (╯ ͠° ͟ʖ ͡°)╯┻━┻ (day 23)

It's an ideal day for pentester when their tools are run as it supposed to be, no bug, no error, everything runs smoothly and the end of the day you can have good night sleep (well who am I kidding, sleep is for the weak)

Unfortunately, it does not always turn out like this right?

In this post I will tell you some of the issues that I usually encounter when I try to do some application testing in android and of course how to solve it, so you don't have to go to google and read a bunch of documentation issues from the official website. It works for me but I cannot assure you that it will 100% work for you have to dig it up by yourself if it's not working.

1st problem: APKTOOL

"apktool" is a tool to reverse engineer your android application, in short, it will convert your apk file into smali bytecode, you can edit it and recompile it back again. But sometimes when i try to build the edited apk, it gives me this bunch of long and hideous error (brut.androidlib.AndrolibException, could not exec....).

Solution:

In order to solve this issue, first you need to locate the local/share directory of apktool and try to find the framework directory and inside there is an apk file, you need to delete this.

PROBLEM SOLVED !!!

2nd problem: Java being .....

I found the following issue when I try to execute appium sign jar binary, it seems that some of the functionality of the program (NoClassDefFoundError, BASE64Encoder) is cut off due to the absent of the class method in java jdk, this is happening due to inconsistencies of java distribution.

Solution:

In order to solve this issue, you need to found the right version java that is compatible with your tools. Mine was compatible when I try to switch to java 8 because by default I use java 11.

3rd problem: failed installation due to older SDK version

This usually happens when you try to install an android application with the target SDK that is higher that your current android vm or device SDK.

[INSTALL_FAILED_OLDER_SDK]

Solution:

To solve this issue you need to lower the sdk version, you need apktool to disassemble the apk. After that go to the resulted directory and try to find apktool.yml and AndroidManifest.xml it should be in the same directory.

Lower the version value of "minsdkversion" in apktool.yml and next is to edit the version value of "android:compileSdkVersion". Rebuild it and it will installed successfully.

Thank you, have a nice day :)

Comments

Having fun analyzing nginx log to find malicious attacker in the net (ง'̀-'́)ง (day 37)

What makes you sleepless at night? is it because of a ghost or scary stories? is it because you have an important meeting tomorrow? or is it because you have an exam? For me, what keeps me up all night is that I keep thinking about what happens to a website that I just created, is it safe from an attacker (certainly not) or did I missing some security adjustments that lead to vulnerability? well I'm not the best secure programmer in the world, I'm still learning and there is a big possibility that I can make a mistake but for me, a mistake can be a valuable investment to myself or yourself to be better so from this idea, I want to know more about what attackers casually do when attacking a website. Here in this post, I'm going to show you how I analyzed attack to the website that I have permission to design and also some interesting findings that I could get from the analysis Background: All of this analysis comes from the traffic that is targeted to th...

Utilize Pwntools for crafting ROP chain :') (day 69)

who doesn't like pwntools? it is a very versatile tool and can be customized according to our need using the python script but did you need to know that pwntools itself can help us to automatically craft a rop chain for us? so in this post, I will show you how to make rop chain less painful and make pwntools do all the heavy lifting. To demonstrate this I will use the binary challenge callme 64 bit from ropemporium link: https://ropemporium.com/challenge/callme.html Crashing the app: Like any other exploitation process, we need to crash the program by generating a long string pattern to determine the offset. based on the information from the above figure we can see that we required to provide 40 bytes of offset Fun stuff: now this where the fun stuff began write the following python script: as in the guideline of the challenged said we need to chain the function call by first to call the callme_one function, callme_two function and then callme_three funct...

Make writing shellcode in linux 32 bit little bit simple (ง'̀-'́)ง (day 53)

Disclaimer: This post is only for education only and not for causing destruction to a lived system. Be smart! In every exploit development process, the shellcode is one of the vital components to making your exploit reliable. Shellcode itself is just basically an assembly instruction that converted into opcodes (the hexadecimal thingy) "\x6a\x66\x58\x99\x6a\x01\x5b\x52\x53\x6a\x02\x89" "\xe1\xcd\x80\x89\xc6\x5f\xb0\x66\xb3\x04\x52\x56" "\x89\xe1\xcd\x80\xb0\x66\x43\x89\x54\x24\x08\xcd" "\x80\x93\x59\xb0\x3f\xcd\x80\x49\x79\xf9\xb0\x0b" "\x52\x68\x2f\x2f\x73\x68\x68\x2f\x62\x69\x6e\x89" "\xe3\x52\x53\xeb\xca"; that will instruct the program what to do next after the exploitation process is done But when it comes to creating it not many people willing to devote their time to learn it, they rather to just used a precompiled shellcode for example that come from http://shell-storm.org/ because they think that is some...

Court of Analysis and Testing

Search This Blog