File: 2352.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 (87 lines) | stat: -rw-r--r-- 2,080 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
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
Rule:

--
Sid:
2192

--
Summary:
This rule generates an event when an attempt is made to exploit a known 
vulnerability in Microsoft RPC DCOM.

--
Impact:
Execution of arbitrary code leading to full administrator access of the 
machine. Denial of Service (DoS).

--
Detailed Information:
A vulnerability exists in Microsoft RPC DCOM such that execution of 
arbitrary code or a Denial of Service condition can be issued against a 
host by sending malformed data via RPC.

The Distributed Component Object Model (DCOM) handles DCOM requests sent
by clients to a server using RPC. A malformed request to an RPC port 
will result in a buffer overflow condition that will present the 
attacker with the opportunity to execute arbitrary code with the 
privileges of the local system account.

This vulnerability is also exploited by the Billy/Blaster worm. The worm
also uses the Trivial File Transfer Protocol (TFTP) to propagate. A 
number of events generated by this rule may indicate worm activity.

--
Affected Systems:
	Windows NT 4.0
	Windows NT 4.0 Terminal Server Edition
	Windows 2000
	Windows XP
	Windows Server 2003

--
Attack Scenarios:
An attacker may make a request for a file with an overly long filename 
via a network share.

--
Ease of Attack:
Simple. Expoit code exists. This is also exploited by a worm.

--
False Positives:
None known.

--
False Negatives:
None known.

--
Corrective Action:
Apply the appropriate vendor supplied patches.

Block access to RPC ports 135, 139 and 445 for both TCP and UDP 
protocols from external sources using a packet filtering firewall.

Block access to port 69 used by the worm to propogate.

Block access to port 4444 used by the worm.

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

--
Additional References:

Microsoft:
http://www.microsoft.com/technet/security/bulletin/MS03-026.asp

CVE:
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2003-0352

Symantec:
http://securityresponse.symantec.com/avcenter/venc/data/w32.blaster.worm.html

--