bugtraq - [OpenPKG-SA-2004.025] OpenPKG Security Advisory (rsync)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <OpenPKG-SA-2004.025__29448.1855271899$1085159100@openpkg.org>
Date: Fri, 21 May 2004 18:20:22 +0200
From: OpenPKG <openpkg@...npkg.org>
To: bugtraq@...urityfocus.com
Subject: [OpenPKG-SA-2004.025] OpenPKG Security Advisory (rsync)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

________________________________________________________________________

OpenPKG Security Advisory                            The OpenPKG Project
http://www.openpkg.org/security.html              http://www.openpkg.org
openpkg-security@...npkg.org                         openpkg@...npkg.org
OpenPKG-SA-2004.025                                          21-May-2004
________________________________________________________________________

Package:             rsync
Vulnerability:       filesystem intrusion
OpenPKG Specific:    no

Affected Releases:   Affected Packages:          Corrected Packages:
OpenPKG CURRENT      <= rsync-2.6.0-20040324     >= rsync-2.6.1-20040428
OpenPKG 2.0          <= rsync-2.6.0-2.0.0        >= rsync-2.6.0-2.0.1
OpenPKG 1.3          <= rsync-2.5.6-1.3.1        >= rsync-2.5.6-1.3.2

Dependent Packages:  none

Description:
  According to a Rsync [0] security advisory [1], versions before
  2.6.1 do not properly sanitize paths when running as a read/write
  daemon without using chroot(2). This allows remote attackers to write
  files outside of the module's path. The OpenPKG default is to run
  a read-only daemon using chroot(2). The Common Vulnerabilities and
  Exposures (CVE) project assigned the id CAN-2004-0426 [2] to the
  problem.

  Please check whether you are affected by running "<prefix>/bin/rpm -q
  rsync". If you have the "rsync" package installed and its version is
  affected (see above), we recommend that you immediately upgrade it
  (see Solution) [3][4].

Solution:
  Select the updated source RPM appropriate for your OpenPKG release
  [5][6], fetch it from the OpenPKG FTP service [7][8] or a mirror
  location, verify its integrity [9], build a corresponding binary RPM
  from it [3] and update your OpenPKG installation by applying the
  binary RPM [4]. For the most recent release OpenPKG 2.0, perform the
  following operations to permanently fix the security problem (for
  other releases adjust accordingly).

  $ ftp ftp.openpkg.org
  ftp> bin
  ftp> cd release/2.0/UPD
  ftp> get rsync-2.6.0-2.0.1.src.rpm
  ftp> bye
  $ <prefix>/bin/openpkg rpm -v --checksig rsync-2.6.0-2.0.1.src.rpm
  $ <prefix>/bin/openpkg rpm --rebuild rsync-2.6.0-2.0.1.src.rpm
  $ su -
  # <prefix>/bin/openpkg rpm -Fvh <prefix>/RPM/PKG/rsync-2.6.0-2.0.1.*.rpm
________________________________________________________________________

References:
  [0] http://rsync.samba.org/
  [1] http://rsync.samba.org/index.html#security_apr04
  [2] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-0426
  [3] http://www.openpkg.org/tutorial.html#regular-source
  [4] http://www.openpkg.org/tutorial.html#regular-binary
  [5] ftp://ftp.openpkg.org/release/1.3/UPD/rsync-2.5.6-1.3.2.src.rpm
  [6] ftp://ftp.openpkg.org/release/2.0/UPD/rsync-2.6.0-2.0.1.src.rpm
  [7] ftp://ftp.openpkg.org/release/1.3/UPD/
  [8] ftp://ftp.openpkg.org/release/2.0/UPD/
  [9] http://www.openpkg.org/security.html#signature
________________________________________________________________________

For security reasons, this advisory was digitally signed with the
OpenPGP public key "OpenPKG <openpkg@...npkg.org>" (ID 63C4CB9F) of the
OpenPKG project which you can retrieve from http://pgp.openpkg.org and
hkp://pgp.openpkg.org. Follow the instructions on http://pgp.openpkg.org/
for details on how to verify the integrity of this advisory.
________________________________________________________________________

-----BEGIN PGP SIGNATURE-----
Comment: OpenPKG <openpkg@...npkg.org>

iD8DBQFArivtgHWT4GPEy58RAnEFAJ44zlK748Yrc6UT/1a1iIESRxJJ+wCePQFs
NmRw90v1Pry2EhTfrDO2D+U=
=zbta
-----END PGP SIGNATURE-----