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
|
Rule:
--
Sid:
245
--
Summary:
This event is generated when an mstream handler attempts to identify active agents.
--
Impact:
Severe. If the listed source IP is in your network, it may be an mstream handler. If the listed destination IP is in your network, it may be an mstream agent.
--
Detailed Information:
The mstream DDoS uses a tiered structure of compromised hosts to coordinate and participate in a distributed denial of service attack. There are "handler" hosts that are used to coordinate the attacks and "agent" hosts that launch the attack. A handler can probe to see if an agent is active by sending it a UDP packet to destination port 10498 with a string of "ping" in the payload.
--
Affected Systems:
Any mstream compromised host.
--
Attack Scenarios:
A mstream handler may probe to see if an agent is active.
--
Ease of Attack:
Simple. mstream code is freely available.
--
False Positives:
None Known.
--
False Negatives:
There are other known handler-to-agent ports in addition to 10498.
--
Corrective Action:
Perform proper forensic analysis on the suspected compromised host to discover the means of compromise.
Rebuild a confirmed compromised host.
Use a packet-filtering firewall to block inappropriate traffic to the network to prevent hosts from being compromised.
--
Contributors:
Original rule writer unknown
Sourcefire Research Team
Judy Novak <judy.novak@sourcefire.com>
--
Additional References:
CVE:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2000-0138
--
|
