Burpsuite is a java based Web Penetration Testing Framework. It will help you to identify vulnerabilities and verify attacks vectors that are affecting web applications. Burpsuite can be configured with Desktop as well as Android mobiles. Through Burpsuite, QA can penetrate web applications on android devices.
To test a web application using the Android device need to configure Burp Proxy Listener to accept the connection on all network interfaces, and then connect both your mobile devices and your computer to the same Wireless network.
This issue may occur because of mismatch of PROXY PORT and PROXY HOSTNAME. The mobile must running on same network on which burpsuite is running. You need to add CA certificate in your mobile browser if working on https.
So i installed the burp certificate on my samsung s3, witch forced me to setup a pin or password lock on my phone. If you manualy install custom certs on the android then you are forced to use a pin/password to protect the phone...
I have not tested those applications that you are referring to, however some applications are implementing certificate pinning. The applications in those cases would stop processing requests is they see that the certificate they receive is not the one expected.
However, the Facebook app was functional, no errors on the phone... but burp was not showing any data stream but some alerts and warnings that maybe burp suite decided to allow the traffic threw... I should have took a closer look at the traffic... seems like hsts stream(just a guess)
Look at any of the talks by Arne Swinnen. He found a slew of issues in the Facebook and Instagram apps and indeed needed to do *something* within Burp, but I can't recall any more what it was. Here's a very recent one:
In this exercise we will run the latest Android Oreo (8.1.0) x86_64 under KVM accelerated Qemu and forward all internet traffic from the Android through Burp Suite running on our Linux x86_64 host. We will be using the following software :
We will be working in a directory called $ANDROID-QEMU (you can call it whatever you want, Im just assigning it a dummy variable name here) and create a virtual disk.img of 10 Gigs size. Also make sure you move your Android iso to this directory
We update the system, test the network etc. Now we are ready for the next stage. That is installing a custom CA into the Android system cacert directory so we can intercept the outgoing/incoming HTTPS traffic in Burp Suite. The only way that I know which works is to add the custom certificate to the root filesystem in /system/etc/security/cacert
Next we need to tell Android to use the Proxy address and port for the WiFi connection, so we simply re-configure the networking (this is a bit clumsy in Android, and took me a while to figure out were the proxy setting was hidden in Oreo)
Thanks for the tutorial i am just want to verify with you if i installed native emulator and installed the burp suite certificate on the emulator i will be able to intercept all the traffic so is this another way or it will solve incoming problem not presented in my mind ?
03c5feb9e7