head 1.4; access; symbols; locks; strict; comment @# @; 1.4 date 2005.12.03.12.19.40; author rse; state Exp; branches; next 1.3; commitid qqpAOapyuzxSmacr; 1.3 date 2005.12.03.11.50.03; author rse; state Exp; branches; next 1.2; commitid irQCXvyd7wvJcacr; 1.2 date 2003.01.22.13.31.38; author rse; state Exp; branches; next 1.1; 1.1 date 2003.01.22.13.01.32; author thl; state Exp; branches; next ; desc @@ 1.4 log @resign after latest adjustments @ text @-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ________________________________________________________________________ OpenPKG Security Advisory The OpenPKG Project http://www.openpkg.org/security.html http://www.openpkg.org openpkg-security@@openpkg.org openpkg@@openpkg.org OpenPKG-SA-2003.005 22-Jan-2003 ________________________________________________________________________ Package: php, apache Vulnerability: buffer overflow in "wordwrap" function OpenPKG Specific: no Affected Releases: Affected Packages: Corrected Packages: OpenPKG CURRENT <= php-4.2.3-20020907 >= php-4.3.0-20021228 <= apache-1.3.27-20021129 >= apache-1.3.27-20021228 OpenPKG 1.2 none N.A. OpenPKG 1.1 <= php-4.2.2-1.1.0 >= php-4.2.2-1.1.1 <= apache-1.3.26-1.1.2 >= apache-1.3.26-1.1.3 OpenPKG 1.0 none N.A. Description: According to a bug report [0] from David F. Skoll a buffer overflow problem exists in the "wordwrap" function of Personal HomePage (PHP) [1], a HTML-embedded scripting language. Thanks to Davids input and help, the source of the problem was tracked down and corrected by the vendor. The Common Vulnerabilities and Exposures (CVE) project assigned the id CVE-2002-1396 [2] to the problem. Please check whether you are affected by running "/bin/rpm -q php". If you have the "php" package installed and its version is affected (see above), we recommend that you immediately upgrade it (see Solution). [3][4] Also run "/bin/rpm -qi apache". If you have the "apache" package installed having the "with_mod_php" option set to "yes" 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] or a mirror location, verify its integrity [8], build a corresponding binary RPM from it [3] and update your OpenPKG installation by applying the binary RPM [4]. For the release OpenPKG 1.1, perform the following operations to permanently fix the security problem (for other releases adjust accordingly). $ ftp ftp.openpkg.org ftp> bin ftp> cd release/1.1/UPD ftp> get php-4.2.2-1.1.1.src.rpm ftp> get apache-1.3.26-1.1.3.src.rpm ftp> bye $ /bin/rpm -v --checksig php-4.2.2-1.1.1.src.rpm $ /bin/rpm -v --checksig apache-1.3.26-1.1.3.src.rpm $ /bin/rpm --rebuild php-4.2.2-1.1.1.src.rpm $ /bin/rpm --rebuild apache-1.3.26-1.1.3.src.rpm $ su - # /bin/rpm -Fvh /RPM/PKG/php-4.2.2-1.1.1.*.rpm # /bin/rpm -Fvh /RPM/PKG/apache-1.3.26-1.1.3.*.rpm ________________________________________________________________________ References: [0] http://bugs.php.net/bug.php?id=20927 [1] http://www.php.net/ [2] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2002-1396 [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.1/UPD/php-4.2.2-1.1.1.src.rpm [6] ftp://ftp.openpkg.org/release/1.1/UPD/apache-1.3.26-1.1.3.src.rpm [7] ftp://ftp.openpkg.org/release/1.1/UPD/ [8] http://www.openpkg.org/security.html#signature ________________________________________________________________________ For security reasons, this advisory was digitally signed with the OpenPGP public key "OpenPKG " (ID 63C4CB9F) of the OpenPKG project which you can find under the official URL http://www.openpkg.org/openpkg.pgp or on http://keyserver.pgp.com/. To check the integrity of this advisory, verify its digital signature by using GnuPG (http://www.gnupg.org/). For instance, pipe this message to the command "gpg --verify --keyserver keyserver.pgp.com". ________________________________________________________________________ -----BEGIN PGP SIGNATURE----- Comment: OpenPKG iD8DBQFDkYymgHWT4GPEy58RArleAKCNSyPltGcoFvhKyLMOnWKU8EUbjwCgp60P dwkVNGKaOuceblz5qJIBRts= =W5bI -----END PGP SIGNATURE----- @ 1.3 log @switch to newer world order of CVE instead of CAN and where no more solution hints are specified in detail and anybody should already memorize this standard text @ text @d90 3 a92 3 iD8DBQE+Lp0igHWT4GPEy58RArl+AJ9/w1U0RwTAHxUooOo/OUpCx9yJagCg8KlV yRQ54kIUxzdQn/bmmfpHZMo= =9ZrR @ 1.2 log @final polishing of PHP SA @ text @d30 1 a30 1 assigned the id CAN-2002-1396 [2] to the problem. d69 1 a69 1 [2] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2002-1396 @ 1.1 log @SA-2003.005-php; CAN-2002-1396 @ text @d1 3 d12 1 a12 1 Package: php d18 2 a19 1 OpenPKG 1.2 none >= php-4.3.0-1.2.0 d21 2 a22 7 OpenPKG 1.0 none >= php-4.0.6-1.0.1 Affected Releases: Dependent Packages: OpenPKG CURRENT <= apache-1.3.27-20021129 >= apache-1.3.27-20021228 OpenPKG 1.2 none >= apache-1.3.27-1.2.0 OpenPKG 1.1 <= apache-1.3.26-1.1.2 >= apache-1.3.26-1.1.3 OpenPKG 1.0 none >= apache-1.3.22-1.0.6 d25 6 a30 7 According to a bug report [0] from David F. Skoll a buffer overflow problem exists in the "wordwrap" function of Personal HomePage (PHP) [1], a an HTML-embedded scripting language. Thanks to David's input and help the source of the problem was tracked down and corrected. The Common Vulnerabilities and Exposures (CVE) project assigned the id CAN-2002-1396 [2] to the problem. d32 2 a33 2 Please check whether you are affected by running "/bin/rpm -q php". If you have the "php" package installed and its version is d36 1 a36 1 d44 2 a45 2 [5], fetch it from the OpenPKG FTP service [6] or a mirror location, verify its integrity [7], build a corresponding binary RPM d55 1 d58 1 d60 1 d63 1 a63 3 Additionally, we recommend that you rebuild and reinstall all dependent packages (see above), if any, too. [3][4] d73 3 a75 2 [6] ftp://ftp.openpkg.org/release/1.1/UPD/ [7] http://www.openpkg.org/security.html#signature d87 7 @