Bug 122511 - CAN-2004-0426 rsync directory traversal
Summary: CAN-2004-0426 rsync directory traversal
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: rsync
Version: 2.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jay Fenlason
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-05-05 12:21 UTC by Mark J. Cox
Modified: 2014-08-31 23:26 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-05-19 19:03:35 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2004:192 0 normal SHIPPED_LIVE Important: rsync security update 2004-05-19 04:00:00 UTC

Description Mark J. Cox 2004-05-05 12:21:15 UTC
There is a security problem in all versions prior to 2.6.1 that
affects only people running a read/write daemon WITHOUT using chroot.
If the user privs that such an rsync daemon is using is anything above
"nobody", you are at risk of someone crafting an attack that could
write a file outside of the module's "path" setting (where all its
files should be stored). Please either enable chroot or upgrade to
2.6.1. People not running a daemon, running a read-only daemon, or
running a chrooted daemon are totally unaffected.

        Affects: 2.1AS 2.1AW 2.1ES 2.1WS
        Affects: 3AS 3ES 3WS

Public: http://rsync.samba.org/#security_apr04

Comment 1 Mark J. Cox 2004-05-19 19:03:35 UTC
An errata has been issued which should help the problem 
described in this bug report. This report is therefore being 
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, 
please follow the link below. You may reopen this bug report 
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2004-192.html



Note You need to log in before you can comment on or make changes to this bug.