One of the first things that we would typically do with Dresser is utilize it to find an attack surface
of the application.
We're looking to attack so the very first thing that you can do here is you could do.
You can run up package stuff list with this will do is it will list off like I said all of the applications
that are currently installed on the device.
And as you recall we were using the diva app which has this package name associated with it.
This package name is what we're going to be using intros her to tell it what application to actually
be scanning.
So there are a few different like information gathering type of commands that we can run through dozer
to be able to get a general information about the application that we're looking to attack.
So the first is going to be run up dot package dot info and then you provide a hyphen a for an argument
to give it the name of the application in wish to scan what this is going to do is it's going to give
you a general high level overview of details about the application.
What that means is you're going to tell you where the data directory is for instance some where the
AP Cape path is what you ideas used with it what version the application is the name of it the process
name you know anything that's really relevant or interesting what permissions it uses for instance as
well.
This gives us sort of like a high level understanding of information about the application it's something
else like he gave us something similar would be an update package that manifests it's when you don't
have to provide an argument you just put in the name of the application and you don't have to put the
hyphen a.
And this will give you the whole manifest file of the application itself.
So if you remember when we did compile the application we can reach this through this manifest inside
of the resources.
So this is the same information as what we're getting here.
The reason why we want to see this is because it can choice information about like game what kind of
permissions are being used what versions of the of the SDK it's targeting and in general it can tell
us a lot of very good pieces of information such as intense that may exist activities that may exist
providers that may exist.
So we get a whole bunch of information about the providers and activities and such.
So if you want take this a little bit further we can look at the actual attack surface to get a more
like generalized format of the like more like a summary I guess it's like a summary of the manifest
file to tell us all the information about the things that we could possibly attack in the application.
So I'm going to run them.
Let's see ops package.
Attack surface and I'll put in the name the application.
What this will do is it will scan the application to tell you information about the attack surface.
So it tells us about activities broadcast receivers content providers in services.
It also tells us that the application is debug able or not.
So each of these are things that we might be able to attack.
This one's got activities and content providers.
These are able to be used for activities typically could show us potential access control violations
whereas content providers could potentially show us some instances where queries might be able to be
used to do a sequel injection and that sort of thing.
So this helps to expose the general attack surface of our application and helps us gather a bit more
information about the application itself.
And then from here we can take a look at some of the different types of attacks that we can do inside
of Dresdner.