File: 1892.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 (71 lines) | stat: -rw-r--r-- 1,475 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
67
68
69
70
71
Rule:

--
Sid:
1892

--
Summary:
This event is generated when SNMP communications contain a NULL value 
the authentication string.

--
Impact:
Medium to Serious. Depending on if the community string was for 
read-only, read-create or read-write an attacker could gain a varying 
level of access to a system.

--
Detailed Information:
An SNMP community string is the authentication process that a host 
running SNMP uses to grant access.

--
Affected Systems:
Numerous. Routers, switches, servers, NAS systems, many others.

--
Attack Scenarios:
An attacker can launch a scan of all network attached devices looking 
for port 161 (UDP) and then attempt to gain access using SNMP.

--
Ease of Attack:
Simple. There are many free SNMP "tree walking" programs, an example of 
such is getIF.

--
False Positives:
None Known

--
False Negatives:
None Known

--
Corrective Action:
Make sure that all devices that have SNMP turned on have complex 
passwords assigned.

Disable unneeded WRITE / CREATE community strings.

Since SNMP traffic is not encrypted, use a packet filtering firewall to 
restrict SNMP communications to the protected network.

--
Contributors:
Sourcefire Research Team
Brian Caswell <bmc@sourcefire.com>
Nigel Houghton <nigel.houghton@sourcefire.com>
Snort documentation contributed by  Mike Rivett ebiz@rivett.org

-- 
Additional References:

GetIF:
http://www.wtcs.org/snmp4tpc/getif.htm

CVE:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-1999-0517

--