squirrelmail CSRF vulnerability May 10 2007 12:02PM
p3rlhax gmail com (1 replies)
Re: squirrelmail CSRF vulnerability May 10 2007 07:37PM
Josh Zlatin-Amishav (josh ramat cc) (1 replies)
On Thu, 10 May 2007 p3rlhax (at) gmail (dot) com [email concealed] wrote:

> IV. DETECTION
>
> Latest version of squirrel mail 1.4.8-4.fc6 and prior are found vulnerable.
>
> V. WORKAROUND
>
> I. Application should check for Referer Header in every post login request.

Referer headers can be forged via Flash, so it is not a good idea to
rely on these for security.

>
> II. Application should use CSRF token which is random enough to identify every legitimate post login request.

According to: http://squirrelmail.org/security/issue/2006-12-02 version
1.4.8-4 is vulnerable to a XSS vulnerability, so an attacker could use the
XSS vector to grab the session token ("CSRF token") and continue the
CSRF attack.

--
- Josh

[ reply ]
Re: squirrelmail CSRF vulnerability May 11 2007 05:41PM
Tim Newsham (newsham lava net) (1 replies)
Re: squirrelmail CSRF vulnerability May 12 2007 07:09PM
Josh Zlatin-Amishav (josh ramat cc) (1 replies)
Re: squirrelmail CSRF vulnerability May 13 2007 06:14PM
Pavel Kankovsky (peak argo troja mff cuni cz)


 

Privacy Statement
Copyright 2010, SecurityFocus