Fingerprintx – Standalone Utility For Service Discovery On Open Ports!

2 years ago

# [![](https://blogger.googleusercontent.com/img/a/AVvXsEiqg-l0VPvOF_PLR1vTbbskTpvqKsJbqLR-x9Dv-XDby3zJYWqNyTFIJi8jGDB7fkElleiDXmRGs7qzj78ekZBwRlvm6j0HzcTaWA1En9ZPeoSZMzQae1AfJEHViz1KZNfLOVLu7IdV6Ct4HmQ0mHGCLP7m5T1OZHNPaBRGs9TYh5SIn7lrsn7k4R4b_Q=w640-h266)]()

`fingerprintx` is a utility similar to [httpx]( “httpx” ) that also supports [fingerprinting]( “fingerprinting” ) services like as RDP, SSH, MySQL, PostgreSQL, Kafka, etc. `fingerprintx` can be used alongside port scanners like [Naabu]( “Naabu” ) to [fingerprint]( “fingerprint” ) a set of ports identified during a port scan. For example, an engineer may wish to scan an IP range and then rapidly fingerprint the service running on all the discovered ports.

# Features

* Fast fingerprinting of exposed services
* Application layer service discovery
* Plays nicely with other [command line]( “command line” ) tools
* Automatic metadata collection from identified services

[]( “Standalone utility for service discovery on open ports! (17)” )[![](https://blogger.googleusercontent.com/img/a/AVvXsEi_oZY–g6jUlxxsW0idLZTr0Pz5lrH8yDV6qIRkkDqo3trQHSVWo2YzEuKOvv8u6OBcx2_MRLwyYKypQH8mpigy4348bHijXPNATi-bxCrEvRGgSMXJoGCZoJzPUnsHuZYiot-QMwaEpGHTY32XuS10PMZ_BjxeajQpPKzYKv–y6xW12b0CGQ0oDzaw=w640-h522)]()

[]( “Standalone utility for service discovery on open ports! (18)” )[![](https://blogger.googleusercontent.com/img/a/AVvXsEgQYxwPjlJFqA7YpK51rfkEokLyRFWUIKR7hnzjMDKXK3BOdzqQ06WniAkiH73B6s5lM9RhnUczkiuqEcblZsGfRBeOp33Y6yDlWVcQbF90yCHJgOigTnSVz70chxInI7gEuHO1hWiVZGfa-chaPlJ5GC_qQ9hoRvT9Taea_Ky5iepcJz3pYbp83YQQ9w=w640-h236)]()

[]( “Standalone utility for service discovery on open ports! (19)” )[![](https://blogger.googleusercontent.com/img/a/AVvXsEhaIh2C3COaq1fA7tOVw5BYwU6JzwnWVDD1TWkMAmaWs1HFIOtf_UVxP9vhRMlSe_dLsvd-pjNwB7kcgyqXoInsxEaXvkEY0Fp_6Vebbu4r35IQqNsNYJ38SL2B2mSm75DdBxeACD6fVplrqs9ucqMA3WN3DlMlfDFNo2S0wK9cP4a6o2swvZaFaDwrsw=w640-h466)]()

## Supported Protocols:

# Installation

From Github

go install github.com/praetorian-inc/fingerprintx/cmd/some-email@example.com

From source (go version > 1.18)

$ git clone some-email@example.com:praetorian-inc/fingerprintx.git
$ cd fingerprintx

# with go version > 1.18
$ go build ./cmd/fingerprintx
$ ./fingerprintx -h

Docker

$ git clone some-email@example.com:praetorian-inc/fingerprintx.git
$ cd fingerprintx

# build
docker build -t fingerprintx .

# and run it
docker run –rm fingerprintx -h
docker run –rm fingerprintx -t praetorian.com:80 –json

# Usage

fingerprintx -h

The `-h` option will display all of the supported flags for `fingerprintx`.

Usage:
fingerprintx [flags]
TARGET SPECIFICATION:
Requires a host and port number or ip and port number. The port is assumed to be open.
HOST:PORT or IP:PORT
EXAMPLES:
fingerprintx -t praetorian.com:80
fingerprintx -l input-file.txt
fingerprintx –json -t praetorian.com:80,127.0.0.1:8000

Flags:
–csv output format in csv
-f, –fast fast mode
-h, –help help for fingerprintx
–json output format in json
-l, –list string input file containing targets
-o, –output string output file
-t, –targets strings target or comma separated target list
-w, –timeout int timeout (milliseconds) (default 500)
-U, –udp run UDP plugins
-v, –verbose verbose mode

The `fast` mode will only attempt to fingerprint the default service associated with that port for each target. For example, if `praetorian.com:8443` is the input, only the `https` plugin would be run. If `https` is not running on `praetorian.com:8443`, there will be NO output. Why do this? It’s a quick way to fingerprint most of the services in a large list of hosts (think the [80/20 rule]( “80/20 rule” )).

# Running Fingerprintx

With one target:

$ fingerprintx -t 127.0.0.1:8000
https://127.0.0.1:8000

By default, the output is in the form: `SERVICE://HOST:PORT`. To get more detailed service output specify JSON with the `–json` flag:

$ fingerprintx -t 127.0.0.1:8000 –json
{“ip”:”127.0.0.1″,”port”:8000,”service”:”http”,”transport”:”tcp”,”metadata”:{“responseHeaders”:{“Content-Length”:[“1154″],”Content-Type”:[“text/html; charset=utf-8″],”Date”:[“Mon, 19 Sep 2022 18:23:18 GMT”],”Server”:[“SimpleHTTP/0.6 Python/3.10.6″]},”status”:”200 OK”,”statusCode”:200,”version”:”SimpleHTTP/0.6 Python/3.10.6″}}

Pipe in output from another program (like [naabu]( “naabu” )):

$ naabu 127.0.0.1 -silent 2>/dev/null | fingerprintx
https://127.0.0.1:8000
ftp://127.0.0.1:21

Run with an input file:

$ cat input.txt | fingerprintx
https://praetorian.com:80
telnet://telehack.com:23

# or if you prefer
$ fingerprintx -l input.txt
https://praetorian.com:80
telnet://telehack.com:23

With more metadata output:

Why Not Nmap?

[Nmap]( “Nmap” ) is the standard for network scanning. Why use `fingerprintx` instead of nmap? The main two reasons are:

* `fingerprintx` works smarter, not harder: the first plugin run against a server with port 8080 open is the http plugin. The default service approach cuts down scanning time in the best case. Most of the time the services running on port 80, 443, 22 are http, https, and ssh — so that’s what `fingerprintx` checks first.
* `fingerprintx` supports json output with the `–json` flag. Nmap supports numerous output options (normal, xml, grep), but they are often hard to parse and script appropriately. `fingerprintx` supports json output which eases integration with other tools in processing pipelines.

# Notes

* Why do you have a `third_party` folder that imports the Go [cryptography]( “cryptography” ) libraries?
* Good question! The `ssh` fingerprinting module identifies the various cryptographic options supported by the server when collecting metadata during the handshake process. This makes use of a few unexported functions, which is why the Go cryptography libraries are included here with an [export.go file]( “export.go file” ).
* Fingerprintx is not designed to identify [open ports]( “open ports” ) on the target systems and assumes that every `target:port` input is open. If none of the ports are open there will be no output as there are no services running on the targets.
* How does this compare to [zgrab2]( “zgrab2” )?
* The `zgrab2` command line usage (and use case) is slightly different than `fingerprintx`. For `zgrab2`, the protocol must be specified ahead of time: `echo praetorian.com | zgrab2 http -p 8000`, which assumes you already know what is running there. For `fingerprintx`, that is not the case: `echo praetorian.com:8000 | fingerprintx`. The “application layer” protocol scanning approach is very similar.

# Acknowledgements

`fingerprintx` is the work of a lot of people, including our great intern class of 2022. Here is a list of contributors so far:

* [praetorian-sohamroy]( “praetorian-sohamroy” )
* [jue-huang]( “jue-huang” )
* [henryjung64]( “henryjung64” )
* [qwetboy10]( “qwetboy10” )
* [jwhenry28]( “jwhenry28” )
* [noahtutt]( “noahtutt” )

**[Download Fingerprintx]( “Download Fingerprintx” )**Read More