File: 2047.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 (74 lines) | stat: -rw-r--r-- 1,476 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
72
73
74
Rule:

--
Sid:
2047

--
Summary:
This event is generated when an attempt is made to access an rsync
module list.

--
Impact:
Information gathering. Possible theft of data.

--
Detailed Information:
rsync is used to synchronize data between two machines across a network.
It achieves this by only sending the differences between the files on 
each host.

Since it does not require both hosts to have the data it is 
synchronizing, it is possible to retrieve a number of files from one 
host without the corresponding files being present on the receiving 
host.

This presents the possibilty of using rsync to receive data from a
protected machine to an external host.

--
Affected Systems:
	All systems using rsync.

--
Attack Scenarios:
The attacker needs to make an rsync request for available modules.

--
Ease of Attack:
Simple

--
False Positives:
Systems using rsync to coordinate sets of data between hosts not in the 
same LAN.

--
False Negatives:
None Known

--
Corrective Action:
Access to files via rsync should be carefully managed using access 
control lists.

The transfer of files from an internal source to an external one should 
be carefully managed using the appropriate firewall rules.

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

--
Additional References:

rsync Home:
http://samba.anu.edu.au/rsync/

University of Washington:
http://www.washington.edu/imap/buffer.html

--