Skip to main content

Drozer Commands - A Security & Attack Framework for Android

What is Drozer?

Drozer is a Security & Attack Framework for Android Application Testing. Drozer is a tool that can be used for Mobile device review , Secure development of applications, BYOD approval and Mobile application testing.

There are 2 Versions of Drozer an Open Source and other one Pro version having following features

  1. Gathering the information about the application
  2. Find the attack surface
  3. Test your Exposure to Public Exploits
  4. Execute dynamic code on a device, to avoid the need to compile and install small test scripts.
  5. Start Android emulators, provisioned with the drozer Agent and the app you want to investigate.
  6. Simulate sensor input, such as GPS, to emulators to test the full attack surface.
  7. View the attack surface as a graph. this will be helpful for the risk assessment reporting.
Drozer is having agent & server architecture so to start with assessment we have to install the agent in the emulator or connected device.

Command to install the Drozer agent on emulator or device

adb install drozer.apk

Start the service on the emulator or device

then give below command
adb forward tcp:31415 tcp:31415

open cmd and browse to drozer directory

To check drozer functionality or device connected

drozer console devices

To connect to the device or emulator

drozer console connect


To get the list of commands/modules

List


To get the help on syntax or parameters needs to be passed to the command
For eg.

run app.package.list -h


To search for an app

run app.package.list -f [keyword]

To get info of an app

run app.package.info -a [package name]

To check the attack surface 

run app.package.attacksurface [package name]


To get info about the activity 

run app.activity.info -a [package name]

To start the activity 

run app.activity.start --component[package name] [activity name]

To get info about providers 

run app.provider.info -a [package name]

To find uri for providers 

run app.provider.finduri [package name]

To get info from providers 

run app.provider.query [uri]

To check path traverssal vul in provider 

run scanner.provider.traversal -a [package name]

To check for Sql injection 

run scanner.provider.injection -a [package name]

To download a file from android device to local machine 

run tools.file.download [source path] [destination path]


To get info abt a service 

run app.service.info -a [package name]


To interact with the service 

run app.service.send [package name] [service name] --msg [msg to service]


To interact with broadcast receiver

run app.broadcast.send --action [action from android_manifest file] --component [package name] [broadcast reciever] --extra string[string to send like in sendind sms we can send phone number for that we need to check source for input parameter]
For eg: run app.broadcast.send --action org.owasp.goatdroid.fourgoats.SOCIAL_SMS --component org.owasp.goatdroid.fourgoats org.owasp.goatdroid.fourgoats.broadcastreceivers.SendSMSNowReceiver --extra string phoneNumber 5554 --extra string message U R Just PWNED!!!!!

Comments

  1. Thank you for sharing such great information. It has help me in finding out more detail about Broadcast App!

    ReplyDelete
  2. It is indeed very useful article! Thanks genius..

    ReplyDelete
  3. Best article, From Many years I work as a app tester in one of the best mobile application testing company in USA...And thing is your article is very helpful to current job or work..Thanks for this

    ReplyDelete
  4. I like your post there is a lot of information about software testing, which i would like to learn, thank you for the great guide. Very useful post and I think it is rather easy to see from the other comments as well that this post is well written and useful. I bookmarked this blog a while ago because of the useful content and I am never being disappointed. Keep up the good work.. QA Services

    ReplyDelete
  5. Great blog. All posts have something to learn. Your work is very good and I appreciate you and hopping for some more informative posts. Desentupidora de esgoto

    ReplyDelete

Post a Comment

Popular posts from this blog

Android Damn Vulnerable App by Security Compass

Tutorial of Android Damn Vulnerable App by Security Compass Introduction: Hi folks, today I am gonna show you some hands on or tutorial of the android app testing which I done during my R&D of android app security testing. Here I will show you from scratch setting up of Lab Server to testing of application. In this you will learn on below topics: 1)Insecure Connection (Traffic over HTTP) 2)Server Side Authorization Issue 3)Insecure File Storage 4)Insecure Logging 5)Encryption of data on device 6)Memory Protection Setting-up of lab (App & Server) First of all you have to download the base app which is damn vulnerable from here . After downloading zip and extracting it you have to build it in .apk format using Eclipse IDE. Now you have to install the app in the emulator before that you have to make sure that you installed SDK and its packages. To install the app you have to start emulator using AVD and clicking on "Start" or by command line emul

OWASP IoT (Internet of Things) Top 10 - A Walkthrough

OWASP IoT (Internet of Things) Top 10 - 2014 Introductions: In Todays world things of everyday are becoming smart, every hour hundreds and thousands of smart devices are being added to the Internet whether it is a Toaster, Camera, Refrigerator, T.Vs, Cars etc. So it can be a target of attackers easily, here comes OWASP IoT Top 10 to address this issue. OWASP IoT Top 10 is designed to make the everyday devices secure on same lines of guidelines by OWASP TOP 10 for applications. The OWASP Internet of Things Top 10 - 2014 is as follows: I1 – Insecure Web Interface I2 – Insufficient Authentication/Authorization I3 – Insecure Network Services I4 – Lack of Transport Encryption I5 – Privacy Concerns I6 – Insecure Cloud Interface I7 – Insecure Mobile Interface I8 – Insufficient Security Configurability I9 – Insecure Software/Firmware I10 – Poor Physical Security  How to test for OWASP IoT Top 10   I1 – Insecure Web Interface: Everyday devices have web ser