cracking damn insecure and vulnerable app

When an intent-filter is used with an application component such as activity, the component is publicly exported. As mentioned in the previous challenge Intent filter should not be treated as a protection mechanism. If you notice the above piece of code, just like the previous challenge the target activity is “protected” with an intent filter.

Once again, a close look at the AndroidManifest.XML file shows the following code. The goal of this challenge is to access the tweeter API Credentials without registering. If you are a registered user, you will have access to the tweeter API Credentials. The following activity appears when you launch this challenge. Challenge 10: “10.ACCESS CONTROL ISSUES – PART 2.” Steps to solve:Ĭlick on “10.ACCESS CONTROL ISSUES – PART 2” in your application. The above command also specifies the intent action using “–a”. $ adb shell am start -n /.APICredsActivity -a .VIEW_CREDS Though the above command works, a more formal way of launching this intent is as shown below. Typing the above command will launch the private activity as shown below. $ adb shell am start /.APICredsActivityĪdb shell: To get shell access on the AVDįinally, “/.APICredsActivity” represents that “APICredsActivity” is the activity that has to be invoked from “” package. This can be achieved by typing the following command in the terminal. For the same reason, this activity is vulnerable and hence it can be invoked by any application from outside. The intent filter should not be treated as a protection mechanism. If you notice the above piece of code, the activity is “protected” with an intent filter. Let’s see how to do it.Ī look at the AndroidManifest.XML file reveals the following entry associated with Vendor API Credentials activity that is shown above. Now, our goal is to access this information, without clicking this button. We can access the API Credentials by clicking “VIEW API CREDENTIALS” button shown in the above activity.ĪPI Credentials are accessible to the user. When the challenge is launched following activity is shown to the users. Here is the functionality of this challenge.

Challenge 9: “9.ACCESS CONTROL ISSUES – PART 1.” Steps to solve:Ĭlick on “9.ACCESS CONTROL ISSUES – PART 1” in your application.

Cracking damn insecure and vulnerable app