File: 1960.txt

package info (click to toggle)
snort 2.9.7.0-5
  • links: PTS, VCS
  • area: main
  • in suites: buster, sid, stretch
  • size: 55,000 kB
  • ctags: 38,464
  • sloc: ansic: 266,667; sh: 12,508; makefile: 2,908; yacc: 497; perl: 496; lex: 261; sed: 14
file content (58 lines) | stat: -rw-r--r-- 1,942 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
Rule:

--
Sid:
1960

--
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) nfsd is listening.


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

--
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 nfsd run.  The nfsd RPC service starts the Network File System (NFS) server daemon that handles file system requests from clients. Once a client mounts an NFS file system, the nfsd daemon handles access to the mount point and associated directories.  Several vulnerabilities are associated with nfsd.

--
Affected Systems:
All hosts running the UNIX portmapper.

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

--
Ease of Attack:
Easy.  

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

--
False Negatives:
This rule detects probes of the portmapper service for nfsd, not probes of the nfsd service itself. Because RPC services often listen on fairly arbitrary ports, it may not be possible to detect misuses of the nfsd service itself. An attacker may attempt to go directly to the nfsd 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:

--