Service and Application Version Detection Part 1 - NM
7 hours 1 minute
Welcome to the end map lesson on service and application version detection.
The main point of this lesson is to show you both why service and application version detection is important
and how to use and map to accomplish it.
There's really only one command line switch that provides this specific capability in and map, but understanding when and how to use it effectively is critical.
I hope this lesson puts it all into context for you.
Here are the learning objectives for this lesson.
First, we'll talk about what service in application version detection is.
Second will discuss why it is both relevant and important.
Third, we'll talk about when and how to use it, including the most important command line options You need to know.
Then I'll provide a couple other command line options that are available,
and we'll finish up this lesson with a lab on service and application version detection. Let's get started.
So what is service in application version detection in and map?
Ultimately, the goal of this phase in an unmapped scan, is to determine what service is and applications air running on target hosts,
additionally, and Map will attempt to determine the version of those service's and applications. It does this by analyzing responses from port scans. Been taking it a step further by interrogating those ports to determine the service or application running on those ports.
This is similar to but far more sophisticated and accurate than typical banner grabbing techniques.
The way in map does. This is by comparing responses to port scans to its built in and map service probes database. It essentially queries its database in order to match expressions from responses
and map. Tries to determine service protocol, application name, version number, host, name, device type and the O s family.
More advanced operating system Discovery will be performed in the next phase of scanning and discussed in the next lesson.
Sometimes network admin, DS and or software companies will run APS, and service is on non standard boards, and map can uncover this. In many cases,
the map also makes use of N. I s Tease common platform in new Marais, Shin or CPD database in order to report in a standardized way a common representation of service and applications and their versions.
The n i s t defined C P. E. S as
a structured naming scheme for information technology systems, software and packages. It goes on to say that the CP includes a formal name format, a method for checking names against the system and a description for binding text and tests to a name.
If you want to read more about their common platform enumeration system, please take a look at the reference on the bullet point of this slide.
Or if you want to read about the details of any maps, service an application version detection navigate to the earl at the bottom of the slide.
The next question you may be interested in answering is why is this relevant and important? Well for network administrators and maps, service and application version detection is a quick and easy way to take an inventory of service. Is an application versions running on hosts? This can help with licensing compliance and vulnerability analysis
for penetration testers.
Versions of service is, and applications can lead to a successful exploitation, including a breach or denial of service attack if that's allowed in their statement of work and or contract.
Additionally, performing this type of scan can help in the improvement of in map
well running these types of scans and end map, We sometimes may get responses from a service that is not match successfully. In those cases, a special fingerprint and u. R L is provided for us to submit details if we're certain about what is running on that port,
the graphic on this slide isn't intended to be your guide for a successful ethical hacker penetration test. I simply wanted to give you a visual ization of the normal progression of in mount scanning based on what we've gone through so far.
The main point is that normally you want to perform service an application version detection after identifying interesting targets and scanning their boards.
Once you found open or open filtered ports through TCP and UDP scans,
you can use version detection to figure out
what is running on those ports.
For those of you familiar with the concept of better grabbing this feature of and map extends your capabilities.
The basic command for running version detection against the target is unmapped space, Dash s Capital V and then the target.
Though the scan is effective at gathering service and application versions, it's pretty slow and somewhat noisy,
like we've covered a lot throughout this course. This basic syntax will run an enemy up since can against 1000 ports and try to determine service in application details based on what is found to be open.
But because it is only performing a sin scan, it is only probing TCP ports and not UDP.
And because there are a lot of critical absent service is that use UDP? You had missed that information with the basic Dash s Capital V scan.
So a better command structure would take into account all the other stuff we've covered so far and would follow the following general structure
Uh, n map space scan technique
space, the ports space s capital V
space, the target. An example would be and map space.
Dash s Capital s space Dash s Capitol, You
space dash P Space Capital T colon 21 comma, 25 comma 80 comma 33 89 comma capital. You
colon 53 comma 88 comma 1 23 space
Dash s Capital V. And then the target.
This example would tighten up the scan considerably, which makes it less detectable and also much faster.
As you can see, we're doing a TCBY scan using TCP ports 2125 80 and 33 89 along with the UDP scan of Ports 88 1 23
Then we're feeding that into the version detection engine with a Dash S Capital V command line switch followed by the target.
We'll go through these and other examples in the lab.
Here are some other command line options that are available to you Inversion detection
dash, dash version, dash intensity, space level
lower levels are effective against many common service's, and higher levels are useful against less. Common service is the trade off is one of noisy nous in time. The higher the intensity, the noise er noisier and longer the scan will take.
The default is seven, which is an excellent balance. For the most part, you'll probably not have to alter version intensity too much.
Dash dash version. Dash light enables light mode. This is shorthand for dash dash version. Dash intensity space, too,
which is fast and may produce the results you're looking for.
Dash Dash version does all will try every single probe and a shorthand for dash dash version, dash intensity, space nine
dash dash version, dust trace will trace version scan activity. It tells unmapped to display extensive debugging information while it's doing its version detection. Scanning
now on to the lab
in this lab will run through the steps mentioned in an earlier slide.
First, we'll do a host Discovery scan.
Then we'll do a port scan. And finally, we'll do some simple and more targeted service and application version detection scans. Let's do it.
Welcome to the end Map service. An application version detection lab
in this lab will run through. A couple of scans were performed in the past. I'm just doing that to demonstrate the normal flow of scans that you might perform on a network.
I'll try to run through these fairly quickly, since you've seen some of them already and will cut the video where the scans take a while.
But I'll point out the amount of time certain scans take so that you can see why targeted scans are much better than simple scans.
All right, so first we're gonna start with Pink Sweep, which is a type of host. Discovery scan will do it in Mt. Dash s n
as you see him in the past, the skin goes really fast. That's why I like it. And it's scanning an entire sub net.
All right, so what I'm interested in and we've targeted this machine in the past
and that iss this del
server, that is, at 1921681.10.
So I'll clear the screen.
And the first thing I want to do now is do a fast TCP and UDP port scan of that server so we'll do it and map Dash s Capital s for the TCP SYN scan
Dash s Capitol. You for the UDP scan dash capital F to make it a fast scan which scans only 100 of the most common ports.
Okay, there you have the results.
And the only reason it really took that long was mostly because I added the dash s Capitol you for the UDP scan. But as I mentioned in the lesson, you DP ports are really important to scan for
when do inversion detection?
there we have all the ports. Okay, so we're gonna refer back to this in a minute,
so I'm not gonna clear the screen,
but what I want to do first
and that is the main command for the service and application version detection, that is, and map Dash s capital V of that server.
I am gonna groups.
I got the wrong I p address.
I'm gonna cut the video on this one because it takes a really long time. And it's important to mention
there's issues with just doing a simple version detection like this. The problem is that it doesn't scan you DP ports.
Instead, it scans of 1000 TCP ports.
So it is slow and it doesn't really catch everything.
Okay, so there you have your results. You can see it took 143.8 seconds.
it's there's some service fingerprints that we can submit to the end map website.
The main thing I want to show you here is
a version detection scan adds this column called version,
and underneath it is What in map has determined is the version of the service is running on these various open ports.
So that's really, really cool information.
and the other thing I want to point out is, if you notice on the Port column, you can see that every one of these is TCP
And so even though this is great information, it's gonna miss UDP port. So doing just a regular dash s Capital V,
um, is gonna miss some critical information about service is that you're gonna be interested in.
So we'll refer back to
this last scan that we did up here, which was a fast TCP and UDP scan. And you can see these three you dp ports along with all of these TCP ports. And I've made note of, um and
I'm going to do a scan that includes both TCP and you critical TCP and UDP ports,
so I'll scroll down to the bottom.