File: 1626.txt

package info (click to toggle)
snort 2.9.7.0-5
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, buster, sid, stretch
  • size: 55,000 kB
  • ctags: 38,464
  • sloc: ansic: 266,667; sh: 12,508; makefile: 2,908; yacc: 497; perl: 496; lex: 261; sed: 14
file content (79 lines) | stat: -rw-r--r-- 1,867 bytes parent folder | download | duplicates (6)
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
Rule:

--
Sid: 1626


--
Summary:
This event is generated when an attempt is made to exploit a potential 
weakness on a host running Microsoft Internet Information Server (IIS). 

--
Impact:
Information gathering possible administrator access.

--
Detailed Information:
This event indicates that an attempt has been made to exploit potential 
weaknesses in a host running Microsoft IIS.

The attacker may be trying to gain information on the IIS implementation
on the host, this may be the prelude to an attack against that host 
using that information.

The attacker may also be trying to gain administrator access to the 
host, garner information on users of the system or retrieve sensitive 
customer information.

Some applications may store sensitive information such as database 
connections, user information, passwords and customer information in 
files accessible via a web interface. Care should be taken to ensure 
these files are not accessible to external sources.

--
Affected Systems:
Any host using IIS.

--
Attack Scenarios:
An attacker can retrieve a sensitive file containing information on the 
IIS implementation. The attacker might then gain administrator access to
the site, deface the content or gain access to a database.

--
Ease of Attack:
Simple.

--
False Positives:
None Known.

--
False Negatives:
None Known.

--
Corrective Action:
Check the IIS implementation on the host. Ensure all measures have been 
taken to deny access to sensitive files.

Ensure that the IIS implementation is fully patched.

Ensure that the underlying operating system is fully patched.

Employ strategies to harden the IIS implementation and operating system.

Check the host for signs of compromise.

--
Contributors:
Sourcefire Research Team
Brian Caswell <bmc@sourcefire.com>
Nigel Houghton <nigel.houghton@sourcefire.com>

--
Additional References:


--