Bug 239054 - mail-client/squirrelmail <1.4.16 Insecure cookie session hijacking (CVE-2008-3663)
|
Bug#:
239054
(CVE-2008-3663)
|
Product: Gentoo Security
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: minor
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: security@gentoo.org
|
Reported By: rbu@gentoo.org
|
|
Component: Vulnerabilities
|
|
|
URL:
http://www.squirrelmail.org/
|
|
Summary: mail-client/squirrelmail <1.4.16 Insecure cookie session hijacking (CVE-2008-3663)
|
|
Keywords:
|
|
Status Whiteboard: B4 [noglsa]
|
|
Opened: 2008-09-29 14:51 0000
|
CVE-2008-3663 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2008-3663):
Squirrelmail 1.4.15 does not set the secure flag for the session
cookie in an https session, which can cause the cookie to be sent in
http requests and make it easier for remote attackers to capture this
cookie.
ANNOUNCE: SquirrelMail 1.4.16 Released
Sep 28, 2008 by Thijs Kinkhorst
The SquirrelMail team is happy to announce the release 1.4.16. The most notable
change is that cookies are now sent with the secure attribute set for
HTTPS-connections, meaning that they cannot leak to an HTTP-connection on the
same SquirrelMail installation. For details see the included ReleaseNotes. We
advise users that offer their SquirrelMail both over HTTP and HTTPS to upgrade.
(In reply to comment #2)
> 1.4.16 in CVS.
>
*ping*
Arches, please test and mark stable:
=mail-client/squirrelmail-1.4.16
Target keywords : "alpha amd64 ppc ppc64 sparc x86"
Ready for vote, I vote YES.
I vote NO on this bug. It's not worse than any of your XSS issues, allowing for
compromise of credentials when visiting a malicious link -- and more so, only
if someone can tap your link.