squirrelmail is vulnerable to information disclosure. It was discovered that SquirrelMail allowed cookies over insecure connections (ie did not restrict cookies to HTTPS connections). An attacker who controlled the communication channel between a user and the SquirrelMail server, or who was able to sniff the user’s network communication, could use this flaw to obtain the user’s session cookie, if a user made an HTTP request to the server.
int21.de/cve/CVE-2008-3663-squirrelmail.html
lists.apple.com/archives/security-announce/2009/Feb/msg00000.html
lists.opensuse.org/opensuse-security-announce/2008-12/msg00003.html
lists.opensuse.org/opensuse-security-announce/2009-02/msg00002.html
secunia.com/advisories/33937
securityreason.com/securityalert/4304
support.apple.com/kb/HT3438
www.nabble.com/ANNOUNCE:-SquirrelMail-1.4.16-Released-td19711998.html
www.redhat.com/security/updates/classification/#moderate
www.securityfocus.com/archive/1/496601/100/0/threaded
www.securityfocus.com/bid/31321
www.squirrelmail.org/security/issue/2008-09-28
www.squirrelmail.org/security/issue/2008-12-04
access.redhat.com/errata/RHSA-2009:0010
exchange.xforce.ibmcloud.com/vulnerabilities/45700
oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A10548