File: 1901.txt

package info (click to toggle)
snort 2.7.0-20.4
  • links: PTS
  • area: main
  • in suites: lenny
  • size: 34,512 kB
  • ctags: 18,772
  • sloc: ansic: 115,404; sh: 10,893; makefile: 1,372; perl: 487; sql: 213
file content (72 lines) | stat: -rw-r--r-- 1,874 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
Rule:

--
Sid:
1901

--
Summary:
This event is generated when a known response to a sucessful attack is
detected.

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

--
Detailed Information:
This event is generated when a known response to a sucessful attack is
detected. 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.

Events generated by rules in attack-responses.rules may indicate that an
attack against a host has been sucessful.

--
Affected Systems:
	Any vulnerable host.

--
Attack Scenarios:
An attacker can access an authentication mechanism and supply his/her
own credentials to gain access. An attacker might also exploit a
weakness in a particular application or piece of software that will
present the opportunity to gain access to the host.

--
Ease of Attack:
Simple. Many exploits exist for various systems and software.

--
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.

Care should be taken to investigate the source of the event. Check for
signs of system compromise in log files. Check for listening services on
high ports.

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

--
Additional References:

--