Everybody welcome to the next video so we're going to be talking briefly about Miss configurations.
Now what are Miss configurations.
It is a configuration of any kind that allows an attacker to gain a foothold into the machine or the
network or on a service.
Now this can vary from anything from a configuration file holding some passwords or maybe configuring
a service in a particular way that makes it vulnerable such as having no authentication enabled to take
it on experience and learn as you go because you're going to find when you're looking up certain services
for example that you'll see oh if it's in this configuration it's honorable to this you can do this
you can do that sometimes looking at the config file understanding what it does is is a good rate is
a good way to go about it because you might see something pretty obvious.
So it's just getting more familiar with with the services and with red teams a little about a lot when
it comes to some of these services.
So knowing how to set up a patchy knowing what the basic config files look like is pretty important
when you're trying to attack a machine that has a patchy.
So knowing where the logs are by default.
Now why is this important does this can be the difference between gaining access or not at all or our
ability to escalate privileges or even use find passwords that are in clear text such as in configuration
files or just sitting on disk.
It's very easy to find for example database passwords tend to be stored in a config file in the web
and for escalating privileges.
This can be something like I said permissions sticky bits et cetera.
So some examples.
So the ATC pass to BD that holds the hashes.
Sometimes this is the shadow.
However if you can add a user to past WD then you can get access to the machine.
So this having global right access by D by accident could allow anybody the ability to write to this
file and create users and set the permissions in groups that they go into which is just as dangerous
because they can set it to the group.
So a configuration file that's viewable without authentication from outside the host so somebody dumped
a config dot I and I file in their web route that their website uses and there's a reason why Web applications
if they have a config file locally they use a dot P HP or some other interpretive language that's not
clear text and if they load the file it doesn't just load the text right on the screen.
So simple stuff like just dumping it into the into a root directory can be a problem or enabling sticky
bits on a binary that can be used to elevate privileges such as V.I. or man or anything else that might
be of use it might be of interest.
So when we go through the rest of the course just keep an eye out for configurations it's always good
to look at what some of the defaults are because sometimes defaults for example usernames and passwords
that are default that are left that way.
That is a mis configuration and you'll find that a lot when you go out and start attacking machines
especially on an enterprise which are looking at Dev networks and Corp networks people bring up services
that have default usernames and passwords all the time and sometimes you can use certain tools in the
web app to start spawning a shell from that point forward.
So it's important just keep this in the back of your mind.
We're going to run into configurations a little bit later such when we get into the post exploitation
side of the course such as for Windows services and stuff like that.
However at least for now just keep this in the back of your head that configuration is something you're
gonna have to learn over time as you get more familiar with some of the products that you're going to
be working with.