head 1.4; access; symbols; locks; strict; comment @# @; 1.4 date 2005.12.03.12.19.42; author rse; state Exp; branches; next 1.3; commitid qqpAOapyuzxSmacr; 1.3 date 2005.12.03.11.50.04; author rse; state Exp; branches; next 1.2; commitid irQCXvyd7wvJcacr; 1.2 date 2004.12.16.21.23.12; author rse; state Exp; branches; next 1.1; 1.1 date 2004.12.16.21.00.59; 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-2004.053 16-Dec-2004 ________________________________________________________________________ Package: php Vulnerability: local and remote execution of arbitrary code OpenPKG Specific: no Affected Releases: Affected Packages: Corrected Packages: OpenPKG CURRENT <= php-4.3.9-20041130 >= php-4.3.10-20041215 <= apache-1.3.33-20041215 >= apache-1.3.33-20041215 OpenPKG 2.2 <= php-4.3.9-2.2.0 >= php-4.3.9-2.2.2 <= apache-1.3.31-2.2.1 >= apache-1.3.31-2.2.3 OpenPKG 2.1 <= php-4.3.8-2.1.2 >= php-4.3.8-2.1.4 <= apache-1.3.31-2.1.6 >= apache-1.3.31-2.1.8 Dependent Packages: none Description: According to a PHP [0] vendor release announcement [1] and a security advisory [2] from Stefan Esser of the Hardened-PHP project, several very serious security issues were fixed in the 4.3.10 maintenance release. The OpenPKG project extracted and backported the fixes. Out of bounds memory write access in shmop_write() and integer overflow/underflow in pack() and unpack() functions. The Common Vulnerabilities and Exposures (CVE) project assigned the candidate id CVE-2004-1018 [3] to the problem and later rejected it because it was not considered to be a serious security issue. Possible information disclosure, double free and negative reference index array underflow in deserialization code. The Common Vulnerabilities and Exposures (CVE) project assigned the id CVE-2004-1019 [4] to the problem. The addslashes() function does not escape \0 correctly. The Common Vulnerabilities and Exposures (CVE) project assigned the canidate id CVE-2004-1020 [5] to the problem and later rejected it because it was not considered to be a serious security issue. Directory bypass in safe_mode execution. The Common Vulnerabilities and Exposures (CVE) project assigned the candidate id CVE-2004-1063 [6] to the problem and later rejected it because it was not considered to be a serious security issue. Arbitrary file access through path truncation. The Common Vulnerabilities and Exposures (CVE) project assigned the candidate id CVE-2004-1064 [7] to the problem and later rejected it because it was not considered to be a serious security issue. Function exif_read_data() suffers from overflow on long sectionname. The Common Vulnerabilities and Exposures (CVE) project assigned the id CVE-2004-1065 [8] to the problem. The "magic_quotes_gpc" functionality could lead to one level directory traversal with file uploads. The Common Vulnerabilities and Exposures (CVE) project assigned no id to the problem. Please check whether you are affected by running "/bin/openpkg 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) [9][10]. Solution: Select the updated source RPM appropriate for your OpenPKG release [11][12], fetch it from the OpenPKG FTP service [13][14] or a mirror location, verify its integrity [15], build a corresponding binary RPM from it [9] and update your OpenPKG installation by applying the binary RPM [10]. For the most recent release OpenPKG 2.2, 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.2/UPD ftp> get php-4.3.9-2.2.2.src.rpm ftp> bye $ /bin/openpkg rpm -v --checksig php-4.3.9-2.2.2.src.rpm $ /bin/openpkg rpm --rebuild php-4.3.9-2.2.2.src.rpm $ su - # /bin/openpkg rpm -Fvh /RPM/PKG/php-4.3.9-2.2.2.*.rpm ________________________________________________________________________ References: [0] http://www.php.net/ [1] http://www.php.net/release_4_3_10.php [2] http://www.hardened-php.net/advisories/012004.txt [3] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2004-1018 [4] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2004-1019 [5] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2004-1020 [6] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2004-1063 [7] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2004-1064 [8] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2004-1065 [9] http://www.openpkg.org/tutorial.html#regular-source [10] http://www.openpkg.org/tutorial.html#regular-binary [11] ftp://ftp.openpkg.org/release/2.2/UPD/php-4.3.9-2.2.2.src.rpm [12] ftp://ftp.openpkg.org/release/2.1/UPD/php-4.3.8-2.1.4.src.rpm [13] ftp://ftp.openpkg.org/release/2.2/UPD/ [14] ftp://ftp.openpkg.org/release/2.1/UPD/ [15] 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 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 iD8DBQFDkY0LgHWT4GPEy58RAvedAJ4w3Rc1jGudLzOaecXAKykNVTc0awCdEE+M NigZ8nnRJT7ho50A3Tbvl6Q= =BlnD -----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 @d120 3 a122 3 iD8DBQFBwfyrgHWT4GPEy58RAl92AKCCyJtcajHH+offSqSYHCTd3EktFgCgq5Np K7JUISp/AjmwMCN/Gz7og7M= =2l65 @ 1.2 log @release OpenPKG Security Advisory 2004.053 (php) @ text @d35 1 a35 1 CAN-2004-1018 [3] to the problem and later rejected it because it was d41 1 a41 1 CAN-2004-1019 [4] to the problem. d45 1 a45 1 CAN-2004-1020 [5] to the problem and later rejected it because it was d49 1 a49 1 and Exposures (CVE) project assigned the candidate id CAN-2004-1063 d55 1 a55 1 CAN-2004-1064 [7] to the problem and later rejected it because it was d60 1 a60 1 CAN-2004-1065 [8] to the problem. d95 6 a100 6 [3] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-1018 [4] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-1019 [5] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-1020 [6] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-1063 [7] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-1064 [8] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-1065 @ 1.1 log @SA-2004.053-php; CAN-2004-1018, CAN-2004-1018, CAN-2004-1019, CAN-2004-1020, CAN-2004-1063, CAN-2004-1064, CAN-2004-1065 @ text @d1 3 d16 7 a22 7 Affected Releases: Affected Packages: Corrected Packages: OpenPKG CURRENT <= php-4.3.9-20041130 >= php-4.3.10-20041215 <= apache-1.3.33-20041215 >= apache-1.3.33-20041215 OpenPKG 2.2 <= php-4.3.9-2.2.0 >= php-4.3.9-2.2.2 <= apache-1.3.31-2.2.1 >= apache-1.3.31-2.2.3 OpenPKG 2.1 <= php-4.3.8-2.1.2 >= php-4.3.8-2.1.4 <= apache-1.3.31-2.1.6 >= apache-1.3.31-2.1.8 d27 2 a28 2 According to a PHP [0] PHP Release Announcement [1] and a security advisory [2] from Stefan Esser of the Hardened-PHP Project several a31 8 Shortly after releasing the initial php-4.3.9-2.2.1 and php-4.3.8-2.1.3 fixes an early adopter reported a bug related to the with_pear option and optimization. At the same time one more security issue was discovered. Also rumors were afloat the Common Vulnerabilities and Exposures (CVE) project is going to withdraw some CANs. The most recent OpenPKG packages have all known issues addressed and use the CVE CAN ids in alignment with the original PHP advisory. d33 24 a56 12 overflow/underflow in pack() and unpack() functions. CAN-2004-1018 [3]. Possible information disclosure, double free and negative reference index array underflow in deserialization code. CAN-2004-1019 [4]. The addslashes() function does not escape \0 correctly. CAN-2004-1020 [5]. Directory bypass in safe_mode execution. CAN-2004-1063 [6]. Arbitrary file access through path truncation CAN-2004-1064 [7]. d59 2 a60 1 CAN-2004-1065 [2]. d62 3 a64 4 The magic_quotes_gpc functionality could lead to one level directory traversal with file uploads. No CVE. Newly discovered TSRM issue. No CVE. d69 1 a69 1 (see Solution) [8][9]. d73 4 a76 4 [10][11], fetch it from the OpenPKG FTP service [12][13] or a mirror location, verify its integrity [14], build a corresponding binary RPM from it [8] and update your OpenPKG installation by applying the binary RPM [9]. For the most recent release OpenPKG 2.2, perform the d92 16 a107 15 [0] http://www.php.net/ [1] http://www.php.net/release_4_3_10.php [2] http://www.hardened-php.net/advisories/012004.txt [3] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-1018 [4] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-1019 [5] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-1020 [6] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-1063 [7] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-1064 [8] http://www.openpkg.org/tutorial.html#regular-source [9] http://www.openpkg.org/tutorial.html#regular-binary [10] ftp://ftp.openpkg.org/release/2.2/UPD/php-4.3.9-2.2.2.src.rpm [11] ftp://ftp.openpkg.org/release/2.1/UPD/php-4.3.8-2.1.3.src.rpm [12] ftp://ftp.openpkg.org/release/2.2/UPD/ [13] ftp://ftp.openpkg.org/release/2.1/UPD/ [14] http://www.openpkg.org/security.html#signature d117 7 @