Subject: [SquirrelMail Security Advisory] Cross Site Scripting in encoded text
Date: November 10, 2004 1:04:51 AM EST
To: email@example.com, firstname.lastname@example.org
Cc: email@example.com, firstname.lastname@example.org, email@example.com
SquirrelMail Security Notice
SquirrelMail is a standards-based webmail package written in PHP4. It
includes built-in pure PHP support for the IMAP and SMTP protocols,
for maximum compatibility across browsers. It has very few
requirements and is very easy to configure and install. SquirrelMail
has all the functionality you would want from an email client,
including strong MIME support, address books, and folder manipulation.
There is a cross site scripting issue in the decoding of encoded text
in certain headers. SquirrelMail correctly decodes the specially
crafted header, but doesn't sanitize the decoded strings.
SquirrelMail 1.4.3a and earlier
SquirrelMail 1.5.1-cvs before 23rd October 2004
A patch has been published to resolve this issue for the SquirrelMail
1.4.3a branch, and can be downloaded from here:
To apply this patch, copy the sm143a-xss.diff file into the base
SquirrelMail directory, and follow the command:
patch -p0 < sm143a-xss.diff
Those using SquirrelMail 1.5.1-cvs should update using CVS, or use a
copy of the latest snapshot downloadable from the SquirrelMail
Special thanks goes to Joost Pol for notifying us about this issue.
The SquirrelMail development team work hard with people reporting
security issues in an attempt to resolve issues. We appreciate those
that are willing to dedicate the time to work with us on any issue
they uncover in the SquirrelMail project.
If any further issues are uncovered, a dedicated mail address can be
used to report the issue. The address is firstname.lastname@example.org.
Jeremy please provide a fixed ebuild.
the second chunk of that patch looks bad... I'm gonna verify upstream...
Stuart, how do you force all vhosts using an old version of a webapp to update to the new one? Can this information be included in the glsa for glsa-check automation?
ppc: please test out 1.4.3a-r2 and mark stable
oh, and for the record I checked the second hunk and I was confused... it's fine...
stable on ppc
GLSA drafted Security please review.