All right, last lecture, we talked about insecurity serialisation, hopefully that makes a lot of
sense to you guys, even if it doesn't sit completely well, hopefully you have a better idea of what
it is and you can speak to it to some degree of competency in an interview or something similar.
So now what we're doing is we're getting into, I think, one of the most well known book classes.
And this is using components with known vulnerabilities.
Right.
This is what you typically think of when you find an exploit on GitHub, write on Twitter and try to
throw that exploit against the Web app, you know, get a rubber shell, maybe exposing sensitive data.
That's typically what we're talking about when we look at this.
But class is very easy to find already written exploits.
That's not a big deal.
Right?
You can find us quite easily.
And this is very prevalent.
It is.
It's a ubiquitous problem.
Some skarner, such as retired gigas helping detection.
And I'll show you that one in a little bit.
And of course, some could have minor impacts, but others can have quite severe impact depending on
the assets that you're protecting.
And how do you make sure you're vulnerable?
You've got to scan, right?
It's one of the things you can do, and this is something I can show quite easily.
So there are tools out there, for example, like shodan and sensors, binary edge.
Right.
These are all tools that will periodically or regularly scan the Internet and look for devices.
So it's kind of like the Google for devices.
You're not looking for Web pages.
You're looking for computers that are public facing Web service databases, things like that.
Another good one is binary edge.
And some of these tools aren't free.
Right?
They're going to cost the money.
But there's a lot of good data here.
And this is a paid application, right?
It's a premium application.
You get what you pay for.
So if you use a free application, you're going to get results that are related to free use a paid application
like berp.
You'll get a higher quality results that here we can see that we have a vulnerable JavaScript dependency
which might befall these vulnerabilities.
And if we're going to extend extender, we can look at a plugin I like called retire, retire.
There it is, retired at Jass.
It's a pro berp extension.
I can install it.
And then when we go back to the target, we right click and we go to Skin Crawl and audit, it's going
to scan this year around.
And we can just keep the default application pool and thread count go to the dashboard, you're going
to eventually start to see a results, Poppy, like using retired.
Yes, it's going to show you vulnerable JavaScript libraries.
You can see it's loaded.
You notice it says on authenticated crawl, when you're running the scan, you typically want to do
a credentialled crawl because when it's credentialed, you have more access to more things, to more
functionality.
You get more coverage in the application because you're now in a position where you have more access.
Right.
So if you're doing a penetration test or red team, see if you have you can get permission to perform
a credentialed audit and a credentialed crawl.
I think this will be the most beneficial to the client that you're supporting.
Right.
So there's not really much to see here.
I mean, just make sure that you guys, you know, you're patching your software, don't use outdated
software, and you make sure that you have a patch management process in place.
And, you know, you're conscious about all of the various attacks and threats that exist and are currently
being exploited in the wild.
And one thing you want to do when this thing is running, you can always look down here in the lab and
you can see the events that are happening.
And then appear in issue activity, you can see the different issues that are found, so, you know,
if there's one tool that you can add to your tools that I strongly suggest you just purchased burp,
it's kind of like a standard tool for penetration tester.
I mean, you can't really do your job well without it.
So make sure you do that and here we can actually see there was another issue that just popped up,
I believe this came from retired James.
But you can see that we have, again, a vulnerable version of jiggery.
And this that's the come from retired.
Yes, we might be able to exploit this and you have some links to some CVS's.
So this is really good and just a really, really easy way to see if you have any vulnerabilities in
your Web site.
But a scam could scam.
All right, guys.
So let's jump into the next picture and we will dig into the whole notion of insufficient monitoring.
All right.
I'll see you guys in the next lecture at about.