1 |
- --------------------------------------------------------------------------- |
2 |
GENTOO LINUX SECURITY ANNOUNCEMENT 200312-03 |
3 |
- --------------------------------------------------------------------------- |
4 |
|
5 |
GLSA: 200312-03 |
6 |
summary: exploitable heap overflow in rsync |
7 |
severity: high |
8 |
date: 2003-12-04 |
9 |
exploit: remote |
10 |
affected: <2.5.6* |
11 |
fixed: >=2.5.7 |
12 |
|
13 |
DESCRIPTION: |
14 |
|
15 |
Rsync version 2.5.6 contains a vulnerability that can be used to run |
16 |
arbitrary code. The Gentoo infrastructure team has some reasonably good |
17 |
forensic evidence that this exploit may have been used in combination with |
18 |
the Linux kernel brk vulnerability (see GLSA 200312-02) to exploit a |
19 |
rsync.gentoo.org rotation server (see GLSA-200312-01.) |
20 |
|
21 |
Please see http://lwn.net/Articles/61541/ for the security advisory released |
22 |
by the rsync development team. |
23 |
|
24 |
SOLUTION: |
25 |
|
26 |
To address this vulnerability, all Gentoo users should: |
27 |
|
28 |
Read GLSA-200312-02 and ensure that all systems are upgraded to a version |
29 |
of the Linux kernel without the brk vulnerability |
30 |
|
31 |
Upgrade to version 2.5.7 of rsync. This can be done by typing: |
32 |
|
33 |
emerge sync; |
34 |
emerge >=net-misc/rsync-2.5.7 |
35 |
|
36 |
Review your /etc/rsyncd.conf configuration file; ensure that the use |
37 |
chroot="no" command is commented out or removed, or change use chroot="no" |
38 |
to use chroot="yes". Then, if necessary, restart rsyncd by typing: |
39 |
|
40 |
/etc/init.d/rsyncd restart |
41 |
|
42 |
//end |