OpenPKG Alert: OpenPKG Security Advisory (squid)
According to a security advisory [0] from the vendor, a vulnerability exists in the URL unescaping logic of the Squid Web Proxy Cache [1]. This bug could allow an attacker to bypass certain access controls by inserting a NUL character into decoded URLs. The Common Vulnerabilities and Exposures (CVE) project assigned the id CAN-2004-0189 [2] to the problem.
|
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
________________________________________________________________________
OpenPKG Security Advisory The OpenPKG Project
http://www.openpkg.org/security.html http://www.openpkg.org
[e-mail:openpkg-security@openpkg.org] [e-mail:openpkg@openpkg.org]
OpenPKG-SA-2004.008 01-Apr-2004
________________________________________________________________________
Package: squid
Vulnerability: URL concealement
OpenPKG Specific: no
Affected Releases: Affected Packages: Corrected Packages:
OpenPKG CURRENT <= squid-2.5.4-20040116 >= squid-2.5.5-20040301
OpenPKG 2.0 <= squid-2.5.4-2.0.0 >= squid-2.5.4-2.0.1
OpenPKG 1.3 <= squid-2.5.3-1.3.0 >= squid-2.5.3-1.3.1
Dependent Packages: none
Description:
According to a security advisory [0] from the vendor, a vulnerability
exists in the URL unescaping logic of the Squid Web Proxy Cache
[1]. This bug could allow an attacker to bypass certain access
controls by inserting a NUL character into decoded URLs. The
Common Vulnerabilities and Exposures (CVE) project assigned the id
CAN-2004-0189 [2] to the problem.
Please check whether you are affected by running "/bin/rpm
-q squid". If you have the "squid" package installed 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][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 http://ftp.openpkg.org
ftp> bin
ftp> cd release/2.0/UPD
ftp> get squid-2.5.4-2.0.1.src.rpm
ftp> bye
$ /bin/openpkg rpm -v --checksig squid-2.5.4-2.0.1.src.rpm
$ /bin/openpkg rpm --rebuild squid-2.5.4-2.0.1.src.rpm
$ su -
# /bin/openpkg rpm -Fvh /RPM/PKG/squid-2.5.4-2.0.1.*.rpm
________________________________________________________________________
References:
[0] http://www.squid-cache.org/Advisories/SQUID-2004_1.txt
[1] http://www.squid-cache.org/
[2] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-0189
[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.3/UPD/squid-2.5.3-1.3.1.src.rpm
[6] ftp://ftp.openpkg.org/release/2.0/UPD/squid-2.5.4-2.0.1.src.rpm
[7] ftp://ftp.openpkg.org/release/1.3/UPD/
[8] ftp://ftp.openpkg.org/release/2.0/UPD/
[9] 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
iD8DBQFAbFtXgHWT4GPEy58RAt1SAKDymC6Hi3okV++USIqJYPwcpdJ63gCePF2s
ErmhPGDaL/b4DSNeE5+LaqI=
=2Odh
-----END PGP SIGNATURE-----
______________________________________________________________________
The OpenPKG Project http://www.openpkg.org
Project Announcement List [e-mail:openpkg-announce@openpkg.org]
[PARSEASHTML]
|
This topic does not have any threads posted yet!
You cannot post until you login.