File: 2016.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 (66 lines) | stat: -rw-r--r-- 1,442 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
Rule:

--
Sid:
2016

--
Summary:
Remote Procedure Call (RPC) is a facility that enables a machine to 
request a service from another remote machine. This is done without the 
request for available services on a host.

--
Impact:
This may be an intelligence gathering activity that could be the prelude
to an attack against a vulnerable service on the host.

--
Detailed Information:
This RPC status request returns information pertaining to available RPC 
services running on a host. This is not an attack against a host by 
itself but may be an intelligence gathering activity in prelude to an 
attack against a vulnerable service running on a target host.

--
Affected Systems:
All machines running RPC services.

--
Attack Scenarios:
The attacker merely needs to request information about services being 
offered on a target machine using "rpcinfo" for example.

--
Ease of Attack:
Simple

--
False Positives:
When seen on a local area network a legitimate rpcinfo request will 

--
False Negatives:
None Known

--
Corrective Action:
RPC services should not be available outside the local area network, 
filter RPC ports at the firewall to ensure access is denied to RPC 
enabled machines.

Disable all RPC services where not needed.

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

--
Additional References:

Whitehats:
http://www.whitehats.com/info/IDS15/

--