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
|
Rule:
--
Sid:
235
--
Summary:
This event is generated when a trinoo DDoS attacker host communicates with a master host.
--
Impact:
Attempted DDoS. If the listed source IP is in your network, it may be a trinoo attacker. If the listed destination IP is in your network, it may be a trinoo master.
--
Detailed Information:
The trinoo DDoS uses a tiered structure of compromised hosts to coordinate and participate in a distributed denial of service attack. At the highest level, attackers communicate with masters to direct them to launch attacks. An attacker may communicate with a master via TCP destination port 27665 with a string of "killme" in the payload. This string is a default mdie password.
--
Affected Systems:
Any trinoo compromised host.
--
Attack Scenarios:
A trinoo attacker will communicate with masters to direct them to launch attacks.
--
Ease of Attack:
Simple. trinoo code is freely available.
--
False Positives:
None Known.
--
False Negatives:
None Known.
--
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
Nigel Houghton <nigel.houghton@sourcefire.com>
Judy Novak <judy.novak@sourcefire.com>
--
Additional References:
CVE:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2000-0138
SecurityFocus:
http://www.securityfocus.com/archive/1/37706
CERT:
http://www.cert.org/incident_notes/IN-99-07.html#trinoo
--
|