| Summary: | mail-client/squirrelmail <1.4.16 Insecure cookie session hijacking (CVE-2008-3663) | ||
|---|---|---|---|
| Product: | Gentoo Security | Reporter: | Robert Buchholz (RETIRED) <rbu> |
| Component: | Vulnerabilities | Assignee: | Gentoo Security <security> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | CC: | eradicator, net-mail+disabled, tv |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://www.squirrelmail.org/ | ||
| Whiteboard: | B4 [noglsa] | ||
| Package list: | Runtime testing required: | --- | |
|
Description
Robert Buchholz (RETIRED)
2008-09-29 14:51:32 UTC
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. 1.4.16 in CVS. (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" ppc64 done amd64 stable x86 stable alpha/sparc stable ppc stable 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. no too and closing. |