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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
From: openpkg at (OpenPKG)
Subject: [OpenPKG-SA-2004.003] OpenPKG Security Advisory (libxml)

Hash: SHA1


OpenPKG Security Advisory                            The OpenPKG Project                   
OpenPKG-SA-2004.003                                          05-Mar-2004

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

Affected Releases:   Affected Packages:          Corrected Packages:
OpenPKG CURRENT      <= libxml-2.6.5-20040126    >= libxml-2.6.6-20040212
OpenPKG 2.0          none                        N.A.
OpenPKG 1.3          <= libxml-2.5.8-1.3.0       >= libxml-2.5.8-1.3.1

Affected Releases:   Dependent Packages:
OpenPKG CURRENT      apache::with_mod_php_dom perl-xml::with_libxml
                     php::with_dom php5::with_xml php5::with_dom cadaver
                     dia kde-libs libgdome libglade libwmf libxslt
                     neon pan ripe-dbase roadrunner scli scrollkeeper
                     sitecopy subversion wv xmlsec xmlstarlet xmlto xmms
OpenPKG 1.3          apache::with_mod_php_dom perl-xml::with_libxml
                     php::with_dom libgdome libwmf libxslt neon sitecopy

  A flaw in the HTTP and FTP client sub-library of libxml2 [0]
  found by Yuuichi Teranishi can be exploited to cause a buffer
  overflow if passed a very long URL [1]. This could be used by
  an attacker to execute arbitrary code on the host computer. The
  Common Vulnerabilities and Exposures (CVE) project assigned the id
  CAN-2004-0110 [2] to the problem.

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

  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 affected release OpenPKG 1.3, perform the following operations
  to permanently fix the security problem (for other releases adjust

  $ ftp
  ftp> bin
  ftp> cd release/1.3/UPD
  ftp> get libxml-2.5.8-1.3.1.src.rpm
  ftp> bye
  $ <prefix>/bin/rpm -v --checksig libxml-2.5.8-1.3.1.src.rpm
  $ <prefix>/bin/rpm --rebuild libxml-2.5.8-1.3.1.src.rpm
  $ su -
  # <prefix>/bin/rpm -Fvh <prefix>/RPM/PKG/libxml-2.5.8-1.3.1.*.rpm

  Additionally, we recommend that you rebuild and reinstall
  all dependent packages (see above), if any, too. [3][4]


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