First published: Thu Aug 13 2009(Updated: )
It was reported that SquirrelMail did not implement protections against cross-site request forgery (CSRF) attacks. This can be exploited to e.g. change user preferences, delete emails, and potentially send emails when a logged-in user visits a malicious web page. Upstream advisory: <a href="http://www.squirrelmail.org/security/issue/2009-08-12">http://www.squirrelmail.org/security/issue/2009-08-12</a> Upstream patch: <a href="http://squirrelmail.svn.sourceforge.net/viewvc/squirrelmail?view=rev&revision=13818">http://squirrelmail.svn.sourceforge.net/viewvc/squirrelmail?view=rev&revision=13818</a> Issue was first addressed in 1.4.20RC1. Secunia advisory: <a href="http://secunia.com/advisories/34627/">http://secunia.com/advisories/34627/</a>
Affected Software | Affected Version | How to fix |
---|---|---|
SquirrelMail | <1.4.20RC1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-517312 is classified as high due to its potential for CSRF attacks.
To fix REDHAT-BUG-517312, upgrade to the latest version of SquirrelMail that contains CSRF protections.
REDHAT-BUG-517312 exposes SquirrelMail to cross-site request forgery (CSRF) attacks that can manipulate user settings and actions.
Versions of SquirrelMail prior to 1.4.20RC1 are affected by REDHAT-BUG-517312.
Due to REDHAT-BUG-517312, an attacker can exploit the vulnerability to change user preferences, delete emails, and send emails.