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: <49E42B8E-6DBC-4B22-948A-41906C54C795@gmail.com>
Date: Sat, 10 Mar 2007 13:03:13 -0800
From: Andrew Farmer <andfarm@...il.com>
To: Scarlet Pimpernel <kishfellow@...oo.com>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: Is OWASP vulnerable ??

On 10 Mar 07, at 09:23, Scarlet Pimpernel wrote:
> Hello all,
>
> There is an undefined function in OWASP website's javascript code  
> (wikibits.js)
> called wgBreakFrames. This can cause potential damage to the site  
> if used maliciously.
>
...
> if (wgBreakFrames) {
...

First of all, that's a variable, not a function. Creating a function  
called "wgBreakFrames" wouldn't execute the function.

Second of all, I'm not really sure how that could be "used  
maliciously". If you're able to inject Javascript into the window  
context, you can already do whatever you like to the user's browser.  
So I'm not quite sure how this is supposed to "cause potential damage  
to the site".

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ