-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathREADME
132 lines (83 loc) · 3.36 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
AMAP v5.4
Application MAPper
- a next generation scanning tool
- by van Hauser and DJ RevMoon / THC <[email protected]>
http://www.thc.org
NOTE: THIS TOOL IS OUTDATED. USE NMAP.
INTRODUCTION
============
This is a public release of Amap. Amap is a next-generation scanning
tool for pentesters. It attempts to identify applications even if they
are running on a different port than normal.
It also identifies non-ascii based applications. This is achieved by
sending trigger packets, and looking up the responses in a list of
response strings.
Without filled databases containing triggers and responses, the tool is
worthless, so I ask you to help us fill the database. How to do this? Well,
whenever a client application connects to a server, some kind of handshake
is exchanged (at least, usually. Syslogd for instance won't say nothing,
and snmpd without the right community string neither). Anyway, amap takes
the first packet sent back and compares it to a list of signature responses.
Really simple, actually. And in reality, it turns out really to be that
simple, at least, for most protocols.
So now, with amap, you can identify that SSL server running on port 3442,
as well as that Oracle listener on port 23.
For unknown protocols, you can use amapcrap, which sends random crap to a
udp, tcp or ssl'ed port, to illicit a response, which you can then
put into the appdefs.trig and appdefs.resp files.
INSTALLING
==========
-> please see the INSTALL file for hints and known problems/solutions
TRIGGERS AND RESPONSES
======================
Take a look at the supplied appdefs.trig and appdefs.resp files.
Much will become clear then.
ESSENTIALS
==========
Amap takes nmap -oM output files as input. You can specify a single IP
address and port)s= on the command line, but usually, you'd run it from a nmap
file, thusly:
# (first "nmap -sS -oM results.nmap -p 1-65535 TARGET" of course)
# amap -i results.nmap -o results.amap -m
or:
# amap 127.0.0.1 443
or:
# amap target 21-6000
Other switches and options can be seen by typing:
# amap -h
HINTS
=====
use the -1 switch, it makes amap much faster!
use the -b switch to let amap print the banners!
use the -q switch to hide messages about closed ports
use the -v switch to get more information
use the -t and -T switches to adapt to your target servers (timeout options)
use the -W switch to update your fingerprint database online
To have a very fast port scanner and banner grabber (but inefficient
application identification):
amap -qbp http TARGET 1-65535
and it gives better results than the "native" banner grab mode:
amap -B -q TARGET 1-65535
CONTRIBUTING
============
Send us the initial packets (sent and received) in tcpdump format for all
wacko, proprietary and obscure applications. Send them to:
[email protected]. Please include application name and version.
A web-enabled interface with uploader will become available soon for your
convenience.
Want to become an amap beta tester? Send an email to [email protected]
COMMERCIAL COMPANIES/SERVICES
=============================
This tool is not completely GPL! See the LICEN[SC]E.* files.
BUGS
====
None :-) Send bugreports to [email protected].
TODO
====
-> see the TODO file
THANKS
======
T1nk, Guido van Rooij, Unicorn, Arhab, Johnny Cyberpunk and many others who
sent us triggers and responses.
Yours,
van Hauser and DJ RevMoon