<<< Date Index >>>     <<< Thread Index >>>

[OpenPKG-SA-2004.009] OpenPKG Security Advisory (mc)

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

________________________________________________________________________

OpenPKG Security Advisory                            The OpenPKG Project
http://www.openpkg.org/security.html              http://www.openpkg.org
openpkg-security@xxxxxxxxxxx                         openpkg@xxxxxxxxxxx
OpenPKG-SA-2004.009                                          05-Apr-2004
________________________________________________________________________

Package:             mc
Vulnerability:       arbitrary code execution
OpenPKG Specific:    no

Affected Releases:   Affected Packages:          Corrected Packages:
OpenPKG CURRENT      <= mc-4.6.0-20040207        >= mc-4.6.0-20040405
OpenPKG 2.0          <= mc-4.6.0-2.0.0           >= mc-4.6.0-2.0.1
OpenPKG 1.3          <= mc-4.6.0-1.3.0           >= mc-4.6.0-1.3.1

Dependent Packages:  none

Description:
  According to a message from Ilya Teterin posted on Bugtraq [0], the
  Midnight Commander application [1] uses a uninitialized buffer to
  handle symlinks in VFS. This allows attackers to execute arbitrary
  code during symlink conversion. The Common Vulnerabilities and
  Exposures (CVE) project assigned the id CAN-2003-1023 [2] to the
  problem.

  Please check whether you are affected by running "<prefix>/bin/rpm
  -q mc". If you have the "mc" 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 mc-4.6.0-2.0.1.src.rpm
  ftp> bye
  $ <prefix>/bin/openpkg rpm -v --checksig mc-4.6.0-2.0.1.src.rpm
  $ <prefix>/bin/openpkg rpm --rebuild mc-4.6.0-2.0.1.src.rpm
  $ su -
  # <prefix>/bin/openpkg rpm -Fvh <prefix>/RPM/PKG/mc-4.6.0-2.0.1.*.rpm
________________________________________________________________________

References:
  [0] http://marc.theaimsgroup.com/?l=bugtraq&m=106399528518704
  [1] http://www.ibiblio.org/mc/
  [2] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2003-1023
  [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/mc-4.6.0-1.3.1.src.rpm
  [6] ftp://ftp.openpkg.org/release/2.0/UPD/mc-4.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@xxxxxxxxxxx>" (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@xxxxxxxxxxx>

iD8DBQFAcWgJgHWT4GPEy58RApYiAJ4nJ+kWlLotGNU8QH50xr+YV+6i4ACg6ILB
9s8Q/a827DQu8aiiPy51KXg=
=VGjp
-----END PGP SIGNATURE-----