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  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)
Subject: [OpenPKG-SA-2004.013] OpenPKG Security Advisory (cvs)

Hash: SHA1


OpenPKG Security Advisory                            The OpenPKG Project                   
OpenPKG-SA-2004.013                                          14-Apr-2004

Package:             cvs
Vulnerability:       remote code execution
OpenPKG Specific:    no

Affected Releases:   Affected Packages:          Corrected Packages:
OpenPKG CURRENT      <= cvs-1.12.6-20040413      >= cvs-1.12.7-20040414
OpenPKG 2.0          <= cvs-1.12.5-2.0.0         >= cvs-1.12.5-2.0.1
OpenPKG 1.3          <= cvs-1.12.1-1.3.3         >= cvs-1.12.1-1.3.4

Dependent Packages:  none

  Sebastian Krahmer from the SuSE Security Team discovered [1] a flaw
  in Concurrent Versions System (CVS) [0] clients where RCS "diff
  files" can create files with absolute pathnames. An attacker could
  create a fake malicious CVS server that would cause arbitrary files
  to be created or overwritten when a victim connects to it. The
  Common Vulnerabilities and Exposures (CVE) project assigned the id
  CAN-2004-0180 [2] to the problem.

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

  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> bin
  ftp> cd release/2.0/UPD
  ftp> get cvs-1.12.5-2.0.1.src.rpm
  ftp> bye
  $ <prefix>/bin/openpkg rpm -v --checksig cvs-1.12.5-2.0.1.src.rpm
  $ <prefix>/bin/openpkg rpm --rebuild cvs-1.12.5-2.0.1.src.rpm
  $ su -
  # <prefix>/bin/openpkg rpm -Fvh <prefix>/RPM/PKG/cvs-1.12.5-2.0.1.*.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 <>


Powered by blists - more mailing lists