So let's see how to install and perform the first scan using the quick scan option.
First, let's see how to download and install OS Zap.
In a browser, I search for Oos Zap.
So, you know, the Google advertisements on top.
But the first link is the link to a wasp that attacked proxy wasps is that attack proxy pages have a
lot of helpful information about the tool.
So by clicking download now, it brings us to the GitHub page of the WASP Zap tool.
Here you have some packages and installers for different platforms so you can choose the appropriate
one and click it to download because I want to use app with my colleague.
I'll download Linux installer or package, so I'll choose the Linux installer.
Now, here, as you see, I already have the package downloaded before, so I'll ignore this stuff.
But importantly, the Linux installer link brings you the file with the DOT S.H. extension.
And when you analyze it with a file, come in, you'll see that it's an executable shell script.
To run it, type dot slash and the file name inside the folder, but hold on, the file does not have
the execution right by default.
So to make it executable by everybody, type C mod 755 filename.
Now it's executable and we can type that and file name to install Zap, but since it's already embedded
in Colly, I'm not going to need to install it again.
So to use oos zap type oos dash zap in anywhere and hit, enter or open the applications menu and type
Owais to find the tool and click its icon to start zap.
As you see, the downloaded version and the embedded version are the same.
So that means we have the current version of his app in our colleague.
So now it asks if you want to save this obsession, I'll choose no, no worries.
I mean, you can say the session, whatever you want.
So now let's see the quick scan option of zap in the QuickStart tab.
Enter the Eurail address of the application, you want to scan and click the attack button to start
the scan.
First, the spider runs to crawl the application.
And at the left pane of the zaps user interface, you'll see the discovered pages of the application.
So now they're yellow or orange flag icons next to some of the pages and folders.
That means ZAP has already found some medium and low level vulnerabilities.
So look at the alerts tab.
You'll see all the vulnerabilities found by now.
And as we said before, ZAP runs the passive scan all the time you use it.
So it's always running in the spidering phase as well.
Now, look at that dam vulnerability web applications folder divi, where you see the only page discovered
is the login page.
The application allows us to see only the login screen if we don't log in to the app that doesn't have
any valid session or credentials.
So it can only find the login page of the DVI app.
And here you can stop or pause the spidering phase by clicking any of the buttons inside the spider
tab.
And to make the demonstration faster, I'll stop this biting phase now.
So as soon as the spidering phase finishes, Zapp starts the active scan phase.
In the active scan tab, there is a button to show the scan progress details and same as spidering,
you can stop or pause the active scan phase by clicking the corresponding button and then the alerts
tab.
We'll see the numbers of the findings are increasing.
So let's look at the scan progress details.
At the left side of the panel there, the names of the vulnerabilities tested by ZAP, the wreck's column
show the number of requests sent to test that vulnerability.
The progress column shows the current status of the progress for that particular vulnerability.
And you can stop or cancel any tests for vulnerability by clicking the small button at the right side
of the row of that vulnerability that continues to the next vulnerability test.
Here it finds some vulnerabilities in high severity level is a reflected excess.
Don't worry, we'll see the vulnerability in detail.
So here's a request sent to test the reflected excess vulnerability.
Now, here's an important warning about the automated tools, the findings of the tool might be a false
positive.
A false positive is where you receive a positive result for test when you should have received a negative
result.
So it sometimes is called a false alarm.
So you have to verify any finding.
So now let's see if the script code executes in this exact test.
It's a get request, so there is not any particular parameter in the body, we can simulate the attack
just by copying and pasting the Yooralla the test request.
Now see how the script runs.
The finding is a true positive.
So I think that's enough.
I don't think there's any need to wait until the end of the scan.