File: 1048.txt

package info (click to toggle)
snort 2.9.2.2-3
  • links: PTS, VCS
  • area: main
  • in suites: wheezy
  • size: 53,752 kB
  • sloc: ansic: 214,625; sh: 13,872; makefile: 2,574; yacc: 505; perl: 496; lex: 260; sql: 213; sed: 14
file content (71 lines) | stat: -rw-r--r-- 1,704 bytes parent folder | download | duplicates (8)
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
Rule:

--
Sid:
1048

--
Summary:
This event is generated when an attempt is made to exploit a known 
vulnerability on a web server or a web application resident on a web
server.

--
Impact:
Information gathering and system integrity compromise. Possible unauthorized
administrative access to the server. Possible execution of arbitrary code of 
the attackers choosing in some cases.

--
Detailed Information:
This event is generated when an attempt is made to compromise a host
running a Web server or a vulnerable application on a web server.

Many known vulnerabilities exist for each implementation and the 
attack scenarios are legion.

Some applications do not perform stringent checks when validating the
credentials of a client host connecting to the services offered on a
host server. This can lead to unauthorized access and possibly escalated
privileges to that of the administrator. Data stored on the machine can
be compromised and trust relationships between the victim server and 
other hosts can be exploited by the attacker.

--
Affected Systems:
	All systems using a web server.

--
Attack Scenarios:
Many attack vectors are possible from simple directory traversal to
exploitation of buffer overflow conditions.

--
Ease of Attack:
Simple. Exploits exist.

--
False Positives:
None known.

--
False Negatives:
None known.

--
Corrective Action:
Ensure the system is using an up to date version of the software and has
had all vendor supplied patches applied.

Check the host logfiles and application logs for signs of compromise.

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

--
Additional References:

--