Welcome back.
Let's discuss security, misconfiguration.
Now, in this lecture, we're going to check out default credentials, vulnerability.
Now you might be asking, well, didn't we already do that?
And isn't this something that belongs to broken authentication or brute force attacks or something like
that?
Well, it's a little bit different.
We covered guessing the full credentials and brute forcing pages of client profiles.
Now we want to take a look at the full credentials, vulnerability for an application that is implemented
in the Web page.
So this is not a user account on a Web page or something like that, which a user sets up.
This is something that the server owner and the Web page owner sets up once using an application within
a Web page.
So we have a simple example right here in our own ASP top10 on our tri hack.
We challenge and we're just going to cover it in this video.
And then we will move on to a different vulnerability, because this is once again GE's default credentials,
vulnerability.
It's rather easy to perform.
All you need to do is try to find the default credentials for a certain application.
Nonetheless, let's go all the way down.
And here it is, task number 19, which is security misconfiguration.
Now, let's start our machine straight straightaway.
And if you'd like, you can go and read through all of this.
We also see that it does mention default passwords as one of the security configurations, whether it's
once again from the user's perspective or from the servers perspective in both ways, there shouldn't
be any default credentials on the Web page.
However, this is something that developers are responsible for because they didn't really change the
default credentials on the application that they hosted on their website and that anyone can access
to.
While our machine is starting, let's read through our challenge, this film showcases a security misconfiguration,
deployed PVM and Hacken by exploiting the security misconfiguration.
OK, so they didn't really tell us anything important.
All they said is to deploy the VMS and find the flak.
Let's wait for a couple more seconds for our VM to start.
And once we get our IP address, let's hope it go right here and.
OK, so this is the application that it opens, we have a login screen, we have swap theme which doesn't
really do anything, and we have changed password.
If you take a look right here, we also have this sign that says pensive notes and it tells us down
here pensive notes and not taking up for people who like to think about their notes.
So we already know this is an app.
Let's try to perhaps Google it.
We go pensive notes inside of our Google.
And the first thing that we see is a GitHub project that is called Pensiveness, let's click on that.
And we get the same message that we got on our Web application, pensive note is a note taking app for
those who want to think and reflect about what they write later on.
So we are on good place.
This is the app we are looking for.
If we go to information and installation down here, we will find this sentence.
This is after downloading and compiling pensive notes log in using the default credentials, pensive
and pensive notes.
So we found default credentials.
Let's see whether they work on our application if we type pencil and then pensive notes.
Well, it does have the credentials and we get our flag right here.
So this is another security risk that could happen once our website is using some type of an application
that has logged in for this can also happen on something like TOMCATS, on IP and all of the other services
that website can have nonetheless.
I just wanted to mention this is another possible vulnerability and that it differs a little bit from
regular default credentials that the user on a Web page can have.
And now that we're done with this, we can move to the next vulnerability, which is called access.
Thank you for watching and we'll see you in the next lecture.