Hi, welcome back to another episode on How to Hack.
So today we'll be discussing about open Web application security project, otherwise known as waps.
So this is the top 10 Web variabilities that we can find across all these different sites.
So more and more websites now are using Web application technology to actually provide information,
provide services and look at even payment systems and so on.
So a lot of different kind of versatility that comes along with Web application services as a result
that we have different kind of attacks that go after many of these sites.
So, of course, the first one you can see over here is injection.
How can we inject something into the site that could bypass some of the different security mechanisms
and be able to pull results, drop tables and so on.
So the list goes on and broken authentication.
I'll be able to try to gain access to the system because you're not able to authenticate us properly
or as intended.
Can we bypass authentication?
No trees on sensitive data exposure.
So again, does it accidentally open up certain directories that would actually allow hackers or users
to browse into those directories, pulling out information of data?
And of course, we also have some external entities.
When you're putting up different kind of XML technology into the site, does it process it correctly?
Is the process or working as intended?
Well, we had actually run certain kind of malicious scripts on it.
Number five, broken access control.
Are you managing the accesses to different users, different identities, different roles of how users
go into your site?
So all this matter in terms of how you're managing DNS and the control of it.
Number six isn't security misconfiguration, which is a very big part because as more and more enterprises
go into cloud, this is the part that we can actually see that some of these servers or instances are
being mis configured.
And this allow hackers to actually go directly into the systems.
So maybe they open up secure, shall they open up telnet.
And there wasn't a ability to stop with first attack from happening and there was seven of Croci scripting.
Are we able to inject our own scripts into the site, changing the behavior of the intended purposes
of different parts of the site, number eight on in security serialisation.
So again, when we upload a data into the system, are we able to change the way it behaves?
Nemani What about components to come alongside with a Web application service?
If you are using different kind of libraries, different kind of plug ins, add ons to your site, already
vulnerable to different kind of attacks as well.
And number 10, how are you logging now?
What is happening to the site?
Did a user fail to authenticate a user?
Actually authentication a few times and he managed to access it.
Is the user accessing the system from a different kind of geolocation?
So all these are things that we have to constantly lock down so that we can perform further analysis
onto the site.
And of course, if you go back into the earlier lecture and tutorial, we will looking at the Web server
architecture, right.
So over here, we've got these on the left side.
We've got all your Web browsers.
So they could be Chrome, Firefox and right at the center, we have all these Web server technology.
So it could be your USP and so on.
In a right state, you go to databases.
So, of course, you could have different databases like Microsoft, SQL microprocessors, equal or
even a newer type, like no sequel on Mongo, DB and so on.
So those are places where we are storing a lot of data.
So again, this is the architecture of a Web server and there's a lot of more things that we can do
with that.
So, of course, if you go back to the earlier lecture and tutorial on SQL injection, so this is a
very simple way.
We're real looking at what's happening across the site and we are able to know what kind of injection
we can put in and this allow us complete access into the system.
All right.
So with that, let us go ahead with the first tutorial.
So over here, I've abstruse shop.
So this allow us an access to a Web application server and Tassell ability to unlock different parts
of the site to SQL injection, to croci scripting and so on.
So, again, this is the place we're going into to try to find more details.
So what we're trying to find here is looking at the search result bar.
So this allow us to put in some kind of input.
There's also an account and login.
So once you're presented with a login page, you're thinking about what kind of database are the using
of the backend and how could you possibly bypass login?
So remember earlier in the electric slide, you could actually see what is happening behind the scene.
And of course, you'll be calling into the database, trying to find details and information.
And all we get to do is enter a single car to test whether this particular login form is vulnerable
to a sequel injection so we can enter or one equal one, which means that this complete statement is
actually true.
And in parser we can just enter one, two, three, four or five, six, seven, eight, for example.
And all we get to do is go ahead and click login and that.
So this would actually allow us access into the system.
And the great thing about All Upstages Shop is that it will actually inform you when a challenge is
complete.
So this is allowing you to learn through a score brought format to know what kind of levels and challenges
there are in order for you to access further into the site.
So we've done I hope you learned something really valuable in today's lecture and tutorial.
So we will be starting this upstairs shop series of a web application penetration testing so that you
can learn more about cybersecurity.
So thank you so much once again for watching.
And if you have any questions, feel free to leave a comment below and I'll try my best to answer any
of your queries.
Remember to like subscribe to channel so that you can be kept abreast of the latest cybersecurity.
Thank you so much once again for watching.