Here's a guide to get started with solving the challenges in DIVA, including the prerequisites mentioned:

Before you dive into solving challenges with DIVA, ensure you have the following tools installed and ready:

1. Genymotion: A fast and easy-to-use Android emulator used to run the DIVA app in a controlled environment. It's preferred for its performance and extensive device emulation capabilities.

2. APKTool: A tool for reverse engineering Android apk files. It allows you to decode resources to nearly original form and rebuild them after making modifications.

3. JD-GUI: A standalone graphical utility that displays Java source codes of “.class” files. You'll use it to inspect the decompiled source code of DIVA.

4. Dex2Jar: Tools to work with android .dex and Java .class files. Dex2Jar allows you to convert DIVA's dex files into jar files for easier analysis with JD-GUI.

5. DIVA APK: The Damn Insecure and Vulnerable App itself. Make sure to download it from a reliable source.

Once you have all the prerequisites, follow these steps to start solving challenges:

1. Set Up Your Environment:

   • Install Genymotion and create a virtual device that matches the Android version DIVA supports.
   • Install APKTool, JD-GUI, and Dex2Jar on your machine.

2. Install DIVA:

   • Drag and drop the DIVA apk file into your Genymotion virtual device to install it, or use ADB (Android Debug Bridge) to install it with the command: adb install path_to_diva_apk.

3. Familiarize Yourself With the Challenges:

   • Open DIVA on your virtual device. Explore the app to understand the types of challenges it offers.

To solve a challenge, you might need to reverse-engineer the app, inspect its code, modify its behavior, or exploit its vulnerabilities. Here's a general approach:

1. Analyze the APK:

   • Use APKTool to decompile the app and inspect its resources and manifest. This can reveal a lot about the app's structure and potential vulnerabilities.
   • Command: apktool d diva.apk

2. Convert and Inspect Code:

   • Use Dex2Jar to convert the APK's dex files into a Java jar file.
   • Command: dex2jar diva.apk
   • Then, use JD-GUI to open the jar file and inspect the decompiled source code for vulnerabilities.

3. Solve Challenges:

   • Each challenge will require a unique approach. For example, you might need to:
     • Modify the app's code or resources to bypass security checks.
     • Inject SQL commands to exploit SQL injection vulnerabilities.
     • Use debugging tools to understand how the app processes data and where it's vulnerable.

4. Test Your Solutions:

   • After modifying the app or preparing an attack, test it on the virtual device to see if your solution works.
   • Use Genymotion and ADB to debug and monitor the app's behavior during your tests.

• Keep Learning: The field of mobile security is vast. Use resources like security blogs, forums, and guides to learn new techniques and stay updated on vulnerabilities.
• Practice Ethically: Only use DIVA and other similar tools in a controlled, legal environment. Never exploit real apps without permission.
• Collaborate: Joining a community of like-minded individuals can accelerate your learning. Share your successes and learn from others' experiences.

Solving challenges in DIVA is a hands-on way to improve your understanding of mobile vulnerabilities and how to exploit them. As you progress, you'll develop a deeper understanding of Android security mechanisms and how to protect against common vulnerabilities.

1. Insecure Logging

2. Hardcoding Issues – Part 1

3. Insecure Data Storage – Part 1

4. Insecure Data Storage – Part 2

5. Insecure Data Storage – Part 3

6. Insecure Data Storage – Part 4

7. Input Validation Issues – Part 1

8. Input Validation Issues – Part 2

9. Access Control Issues – Part 1

10. Access Control Issues – Part 2

11. Access Control Issues – Part 3

12. Hardcoding Issues – Part2

13. Input Validation Issues – Part

https://www.genymotion.com/product-desktop/download/

you can download it from above link.

install android emulator in genymotion and setup emulator to proxy through the burp suite, you can take help from here

apt install apktool

apt install jd-gui

http://www.payatu.com/wp-content/uploads/2016/01/diva-beta.tar.gz

download it from above link

use below command to install apk into emulator.

adb shell install <apk-name>

adb can be found in Genymotion/Tools directory

1. After download apk, extract it using normal extracting methods and rename it to diva-beta1

2. Use apktool to decompile apk

   apktool d <apk>

3. Now move to diva-beta directory and open AndroidManifest.xml.

4. Now move to diva-beta1 directory and run below command in this directory.

   d2j-dex2jar classes.dex

5. Open classes-dex2jar.jar file located within this directory.

   jd-gui classes-dex2jar.jar

Congratulations you setup lab environment, now proceed to exploitation section.

1. Insecure Logging:

enter any number in input filed and click on checkout

check logs using below command and replace "123456" with your input, you will see your input reflected in logs

2. Hardcoding Issues – Part 1

this is hardcoding challenge this mean the Vendor Key is hardcoded in the application. In order to get the hardcoded key we need to do Reverse Engineering of this application.

so go to your jd-gui screen and you will see harcoreded credentials here.

3. Insecure Data Storage – Part 1:

Enter your creds in input fileds.

review the source code of this activity. We can see that credentials are stored in Shared Preferences.

Now go to this folder and you will see credentials.

4. Insecure Data Storage – Part 2:

This is similar challenge to previous one but credentials are stored in different location.

Enter your creds in input fileds.

This time credentials were stored in database ids2 and in its myuser table

Goto to database folder in /data/data and you will see your credentials.

5. Insecure Data Storage – Part 3:

Enter the credentials from application.

The credentials were stored in temporary file

Let’s access those temporary file from shell.

6. Insecure Data Storage – Part 4:

Enter the credentials from application.

The app is storing credentials in external storage.

We got the location, now access them from shell.

7. Input Validation Issues – Part 1:

Now try to enter admin in input field, you will get details about admin user.

Hmmm, it is looking fetching data from database, let's try sql injection

sql injection was successful, we got all users detail.

8. Input Validation Issues – Part 2:

In this challenge we have to access local files using URL,

Let’s try to get file info from local storage other then valid url.

Note: the file you are trying to read will also exist in /sdcard, if not create one for pratice.

9. Access Control Issues – Part 1:

Accessing credentials from “View API Credentials” Button is completely legal. There is no issue in it. We need to check that can we directly access credentials without going through this activity or this checkpoint.

we look into "AndroidManifest.xml" for any exported android component, if any component is exported then it can be accessible outside the app.

we got one activity exported in "AndroidManifest.xml"

Lets open the activity outside the app context. We can see activity launched with sensitive activity without directly interacting with app.

10. Access Control Issues – Part 2:

This is same as above Vulnerablebut there is a slight twist.

We see into "AndroidManifest.xml" again and found another exported activity.

Now try to start this activity.

Oh no its asking for pin, we have to bypass this pin to access sensitive activity.

Now look into decompiled code using jd-gui, we can see that we have to provide some string and boolean value, but which is.

We see APICreds2Activity (which is much silialr as intent defined in AndroidManifest.xml) in decompiled code, now look into it, we get bool value we have need to change it from false to true, but we still need some string parameter.

we got some number in getString() function.

There is references in android in R.class, we check this for any reference related to above got number, yaa hooo, we got string which we can used as a paramter to access our secret activity.

Now its time to open the activity, Now arrange all got info into one command to get access.

11. Access Control Issues – Part 3:

Now again come to AndoirdManifest.xml and this time we see another component exported and which is provider component, this components manages access to data.

Now check decompiled code for this notesprovider.

We got content provider uri in decompiled code.

Now lets try to acees it otside the app.

12. Hardcoding Issues – Part2:

We have to find vendor pin in order to access it,

We can see its accesing Divajni class, click on it.

We can see in this code that , it is accessing divajni library.

Now goto diva-lab1/lib/<anyfolder> and you will got libdivajni.so file.

Now string to it and you got some string different then others, this string is a key to success.

Input htis key into the app.

13. Input Validation Issues – Part 3:

We have to crash this app by Dosing it,

NOw generate 60 characters and add into the input filed and click on button.