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
|
Rule:
--
Sid:
1520
--
Summary:
This event is generated when an attempt is made to access server-info.
Using the Apache webserver, this url is generally handled by the
mod_info module, which will happily disclose valuable information about
your webserver which may aid in their attack.
--
Impact:
Information disclosure.
--
Detailed Information:
The mod_info module "provides a comprehensive overview of the server
configuration including all installed modules and directives in the
configuration files" for the Apache webserver. Successfully accessing the url
that is handle by mod_info may give an attacker valuable information about
the server.
If mod_info is in use and the attacking host is allowed to access it,
every possible configuration option that the Apache server is using can
be viewed. This includes ACLs, modules, file and directory names, and
other valuable information that will help an attacker determine ways of
attacking the server.
--
Affected Systems:
Apache webservers with mod_info enabled.
--
Attack Scenarios:
As part of an attack against an Apache webserver, an attacker may try to
access "/server-info" which is typically handled by the mod_info module. If
sucessful, this will give valuable information about the webserver for
use in further attacks.
--
Ease of Attack:
Simple. No exploit software is required.
--
False Positives:
Few, but certainly possible. Since this rule only checks for the
existance of "/server-info" in the url, any url containing that string will
trigger this rule. A few common false positives may include urls like:
http://victim/server-info/contact.html
http://victim/really/long/directory/server-info.html
--
False Negatives:
None Known
--
Corrective Action:
Determine if server-info exists on the victim in question, and if the attacker
is allowed to access it.
If mod_info is necessary on this server, consider restricting access to
it via Apache directives, i.e.:
<Location /server-info>
SetHandler server-info
Order deny,allow
Deny from all
Allow from .yourdomain.net
</Location>
--
Contributors:
Snort documentation contributed by Jon Hart <warchild@spoofed.org>
Sourcefire Vulnerability Research Team
Brian Caswell <bmc@sourcefire.com>
Nigel Houghton <nigel.houghton@sourcefire.com>
--
Additional References:
Apache:
http://httpd.apache.org/docs/mod/mod_info.html
--
|
