full-disclosure - [OpenPKG-SA-2004.018] OpenPKG Security Advisory (proftpd)

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 for Android: free password hash cracker in your pocket

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

From: openpkg at openpkg.org (OpenPKG)
Subject: [OpenPKG-SA-2004.018] OpenPKG Security Advisory (proftpd)

-----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.018                                          30-Apr-2004
________________________________________________________________________

Package:             proftpd
Vulnerability:       privilege escalation
OpenPKG Specific:    no

Affected Releases:   Affected Packages:        Corrected Packages:
OpenPKG CURRENT      <= proftpd-1.2.9-20040207 >= proftpd-1.2.10rc1-20040429
OpenPKG 2.0          <= proftpd-1.2.9-2.0.0    >= proftpd-1.2.9-2.0.1
OpenPKG 1.3          N.A.                      none

Dependent Packages:  none

Description:
  A portability workaround was applied in version 1.2.9 of the FTP
  server ProFTPD [1]. As a side-effect, CIDR based (aaa.bbb.ccc.ddd/NN)
  ACL entries in "Allow" and "Deny" directives act like an "AllowAll"
  directive and so FTP clients are granted access to files and
  directories although the server configuration might explicitly deny
  this [2].

  Please check whether you are affected by running "<prefix>/bin/rpm -q
  proftpd". If you have the "proftpd" 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], fetch it from the OpenPKG FTP service [6] or a mirror location,
  verify its integrity [7], 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 proftpd-1.2.9-2.0.1.src.rpm
  ftp> bye
  $ <prefix>/bin/openpkg rpm -v --checksig proftpd-1.2.9-2.0.1.src.rpm
  $ <prefix>/bin/openpkg rpm --rebuild proftpd-1.2.9-2.0.1.src.rpm
  $ su -
  # <prefix>/bin/openpkg rpm -Fvh <prefix>/RPM/PKG/proftpd-1.2.9-2.0.1.*.rpm
________________________________________________________________________

References:
  [1] http://www.proftpd.org/
  [2] http://bugs.proftpd.org/show_bug.cgi?id=2267
  [3] http://www.openpkg.org/tutorial.html#regular-source
  [4] http://www.openpkg.org/tutorial.html#regular-binary
  [5] ftp://ftp.openpkg.org/release/2.0/UPD/proftpd-1.2.9-2.0.1.src.rpm
  [6] ftp://ftp.openpkg.org/release/2.0/UPD/
  [7] 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>

iD8DBQFAkj15gHWT4GPEy58RAqZSAJ92m41X9yTMz5SVG1uKyjdnBxZrJwCgn7U/
3BHlVabxWM1RDqtmSv6OqMI=
=WZLY
-----END PGP SIGNATURE-----