First published: Fri Sep 26 2008(Updated: )
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. Reference: BUGTRAQ:20080922 Squirrelmail: Session hijacking vulnerability, <a href="https://access.redhat.com/security/cve/CVE-2008-3663">CVE-2008-3663</a> Reference: URL:<a href="http://www.securityfocus.com/archive/1/archive/1/496601/100/0/threaded">http://www.securityfocus.com/archive/1/archive/1/496601/100/0/threaded</a> Reference: MISC:<a href="http://int21.de/cve/CVE-2008-3663-squirrelmail.html">http://int21.de/cve/CVE-2008-3663-squirrelmail.html</a> Reference: BID:31321 Reference: URL:<a href="http://www.securityfocus.com/bid/31321">http://www.securityfocus.com/bid/31321</a>
Affected Software | Affected Version | How to fix |
---|---|---|
SquirrelMail |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-464183 is considered high due to the potential for session hijacking.
To fix REDHAT-BUG-464183, upgrade SquirrelMail to a version that sets the secure flag on session cookies.
The impact of REDHAT-BUG-464183 is that it allows remote attackers to capture session cookies, leading to possible session hijacking.
SquirrelMail version 1.4.15 is affected by REDHAT-BUG-464183.
Yes, REDHAT-BUG-464183 can be exploited remotely, allowing attackers to intercept session cookies.