need to bump squirrelmail to 1.4.3 (though it is not yet available for download at the time of this bug filing). Date: Fri, 30 Apr 2004 15:22:47 -0500 From: Jonathan Angliss <jon@squirrelmail.org> To: Alvin Alex <alvin_gboy@hotmail.com> Cc: bugtraq@securityfocus.com Subject: Re: SquirrelMail Cross Scripting Attacks.... Hello Alvin, On Thursday, April 29, 2004, Alvin Alex wrote... > SquirrelMail latest version (although is tested on version 1.4.2) is > prone to many cross scripting attacks that can be used to steal user > cookies. [..] > Squirrel Mail Coders have been informed of this vulnerability but > the vulnerability still exists in their latest version. PLEASE in future notify us before posting bug reports so we can ensure a fix is in place... The 1.4.3 release which will be out shortly will fix this issue, along with a number of other XSS issues. While we had been notified of the issue, we were holding off on announcing the issue until a fix was in place. -- Jonathan Angliss (jon@squirrelmail.org)
1.4.3-rc1 is now available. From: Jonathan Angliss <jon@squirrelmail.org> Date: May 10, 2004 10:30:50 PM EDT To: squirrelmail-users@lists.sourceforge.net, squirrelmail-devel@lists.sourceforge.net, <squirrelmail-plugins@lists.sourceforge.net>, <squirrelmail-announce@lists.sourceforge.net> Subject: [SM-ANNOUNCE] SquirrelMail 1.4.3-RC1 Release Good Evening all, I'd like to introduce the SquirrelMail 1.4.3 Release Candidate 1 to the general public. This is a testing release before the final version. In This Release --------------- This release contains a number of bug fixes, including a number of XSS fixes, and a well hidden SQL injection issue discovered by Eyal Udassin (eyal [at] bazman.co.il). There are also a number of minor user interface tweaks and some minor feature enhancements, including some things around date handling of incoming emails. More details on updates are in the ChangeLog which can be seen here: http://www.squirrelmail.org/changelog.php We'd like all to test as soon as possible. To emphasis again, this is a release candidate. A proper release note will be included with the final release. Thanks All, The SquirrelMail Development Team ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 -- squirrelmail-announce mailing list List Address: squirrelmail-announce@lists.sourceforge.net List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-announce
Ok, this is ready for a GLSA advisory: squirrelmail-1.4.2-r4.ebuild -> squirrelmail-1.4.3_rc1.ebuild squirrelmail-1.4.2-r5.ebuild -> squirrelmail-1.4.3_rc1-r1.ebuild
glsa 200405-16 sent as: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Gentoo Linux Security Advisory GLSA 200405-16 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - http://security.gentoo.org/ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Severity: Normal Title: Multiple XSS Vulnerabilities in SquirrelMail Date: May 21, 2004 Bugs: #49675 ID: 200405-16 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Synopsis ======== SquirrelMail is subject to several XSS and one SQL injection vulnerability. Background ========== SquirrelMail is a webmail package written in PHP. It supports IMAP and SMTP, and can optionally be installed with SQL support. Affected packages ================= ------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 net-mail/squirrelmail <= 1.4.2 >= 1.4.3_rc1 Description =========== Several unspecified cross-site scripting (XSS) vulnerabilities and a well hidden SQL injection vulnerability were found. An XSS attack allows an attacker to insert malicious code into a web-based application. SquirrelMail does not check for code when parsing variables received via the URL query string. Impact ====== One of the XSS vulnerabilities could be exploited by an attacker to steal cookie-based authentication credentials from the user's browser. The SQL injection issue could potentially be used by an attacker to run arbitrary SQL commands inside the SquirrelMail database with privileges of the SquirrelMail database user. Workaround ========== There is no known workaround at this time. All users are advised to upgrade to version 1.4.3_rc1 or higher of SquirrelMail. Resolution ========== All SquirrelMail users should upgrade to the latest stable version: # emerge sync # emerge -pv ">=net-mail/squirrelmail-1.4.3_rc1" # emerge ">=net-mail/squirrelmail-1.4.3_rc1" References ========== [ 1 ] SquirrelMail 1.4.3_rc1 release annoucement http://sourceforge.net/mailarchive/forum.php?thread_id=4199060&forum_id=1988 [ 2 ] Bugtraq security annoucement http://www.securityfocus.com/bid/10246/ [ 3 ] CERT description of XSS http://www.cert.org/advisories/CA-2000-02.html Availability ============ This GLSA and any updates to it are available for viewing at the Gentoo Security Website: http://security.gentoo.org/glsa/glsa-200405-16.xml Concerns? ========= Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at http://bugs.gentoo.org. License ======= Copyright 2004 Gentoo Technologies, Inc; referenced text belongs to its owner(s). The contents of this document are licensed under the Creative Commons - Attribution / Share Alike license. http://creativecommons.org/licenses/by-sa/1.0 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (Darwin) iD8DBQFArkYbnt0v0zAqOHYRAsbCAKCgFyTi3benON9CIPi1Z/Zs85KXFgCeKOeF SbrQqZQoiK2N2QPn8FuWUHw= =HZpB -----END PGP SIGNATURE-----
I think there is an error in the GLSA... 1.4.2-r1 is an affected version, but it's not in the published affected range (<=1.4.2). Furthermore, we should probably have waited for ppc stable before issuing the GLSA. ppc : please mark >=1.4.3_rc1 stable ASAP so we can issue the errata GLSA.
please remove 1.4.2-r1 it's not needed any more
I'll take a look at it tonight and mark it stable on ppc if I have no issues.
Seems lu_zero beat me to it, marked stable on ppc now :)
GLSA 200405-16:02 errata
*** Bug 52434 has been marked as a duplicate of this bug. ***
