Visit our newest sister site!
Hundreds of free aircraft flight manuals
Civilian • Historical • Military • Declassified • FREE!

TUCoPS :: Linux :: Apps N-Z :: bt826.txt

openssh info leak

Hash: SHA1


OpenPKG Security Advisory                            The OpenPKG Project                   
OpenPKG-SA-2003.035                                          06-Aug-2003

Package:             openssh
Vulnerability:       information leakage
OpenPKG Specific:    no

Affected Releases:   Affected Packages:          Corrected Packages:
OpenPKG CURRENT      <= openssh-3.6.1p1-20030423 >= openssh-3.6.1p2-20030429
OpenPKG 1.3          none                        N.A.
OpenPKG 1.2          <= openssh-3.5p1-1.2.1      >= openssh-3.5p1-1.2.2

Dependent Packages:  none

  According to a security advisory [0], an information
  leakage exists in OpenSSH [1] 3.6.1p1 and earlier if PAM support
  is enabled. When a user does not exists, an error message is sent
  immediately (without any delays) which allows remote attackers to
  determine valid usernames via a timing attack. OpenPKG installations
  are only affected if the package was build with option "with_pam"
  set to "yes" -- which is not the default. The Common Vulnerabilities
  and Exposures (CVE) project assigned the id CAN-2003-0190 [2] to the
  We could only reproduce the problem on Linux. FreeBSD and Solaris are
  not vulnerable, the patch does not affect their behaviour. However,
  the problem is related to the PAM configuration, not the operating
  system. Using a non-default configuration might leak information on
  other operating systems, too. On Linux systems, a valid workaround is
  to add a "nodelay" option to the auth.

  Please check whether you are affected by running "<prefix>/bin/rpm -q
  openssh". If you have the "openssh" package installed and its version
  is affected (see above), we recommend that you immediately upgrade it
  (see 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 current release OpenPKG 1.2, perform the following operations
  to permanently fix the security problem (for other releases adjust

  $ ftp
  ftp> bin
  ftp> cd release/1.2/UPD
  ftp> get openssh-3.5p1-1.2.2.src.rpm
  ftp> bye
  $ <prefix>/bin/rpm -v --checksig openssh-3.5p1-1.2.2.src.rpm
  $ <prefix>/bin/rpm --rebuild openssh-3.5p1-1.2.2.src.rpm
  $ su -
  # <prefix>/bin/rpm -Fvh <prefix>/RPM/PKG/openssh-3.5p1-1.2.2.*.rpm


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

Comment: OpenPKG <>


TUCoPS is optimized to look best in Firefox® on a widescreen monitor (1440x900 or better).
Site design & layout copyright © 1986-2015 AOH