bugtraq - Re: squirrelmail CSRF vulnerability

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.61.0705101524140.2078@zur>
Date: Thu, 10 May 2007 15:37:11 -0400 (EDT)
From: Josh Zlatin-Amishav <josh@...at.cc>
To: p3rlhax@...il.com
Cc: bugtraq@...urityfocus.com
Subject: Re: squirrelmail CSRF vulnerability

On Thu, 10 May 2007 p3rlhax@...il.com 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