File: 1262.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 (61 lines) | stat: -rw-r--r-- 1,979 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
Rule:

--
Sid:
1262

--
Summary:
This event is generated when an attempt is made through a portmap GETPORT request to discover the port where the Remote Procedure Call (RPC) admind is listening.

--
Impact:
Information disclosure.  This request is used to discover which port admind is using.  Attackers can also learn what versions of the admind protocol are accepted by admind.

--
Detailed Information:
The portmapper service registers all RPC services on UNIX hosts. It can be queried to determine the port where RPC services such as admind run.  The admind RPC service is used by some UNIX hosts to remotely perform distributed system administration tasks such as adding new users.  If weak authentication is used, it may be possible for a malicious user to perform remote administration.

--
Affected Systems:
Any host running admind with weak authentication.

--
Attack Scenarios:
An attacker can query the portmapper to discover the port where admind runs.  This may be a precursor to accessing admind.

--
Ease of Attack:
Simple.  

--
False Positives:
If a legitimate remote user is allowed to access admind, this rule may trigger.

--
False Negatives:
This rule detects probes of the portmapper service for admind, not probes of the admind service itself. Because RPC services often listen on fairly arbitrary ports, it may not be possible to detect misuses of the admind service itself. An attacker may attempt to go directly to the admind port without querying the portmapper service, which would not trigger the rule.

--
Corrective Action:
Limit remote access to RPC services.

Filter RPC ports at the firewall to ensure access is denied to RPC-enabled machines. 

Disable unneeded RPC services.

--
Contributors:
Original rule written by Max Vision <vision@whitehats.com>
Modified by Brian Caswell <bmc@sourcefire.com>
Sourcefire Research Team
Judy Novak <judy.novak@sourcefire.com>

--
Additional References:

Arachnids 
http://www.whitehats.com/info/IDS18


--