bugtraq - Re: google xss

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] [day] [month] [year] [list]

Message-ID: <c53dd6980604120534n33542a82u9f88af86684562c1@mail.gmail.com>
Date: Wed, 12 Apr 2006 15:34:55 +0300
From: "Vladimir Levijev" <vladimir.levijev@...il.com>
To: pagvac <unknown.pentester@...il.com>
Cc: "Andy Meyers" <andy.meyers@...hmail.com>,
	bugtraq@...urityfocus.com
Subject: Re: google xss

On 4/10/06, pagvac <unknown.pentester@...il.com> wrote:

> Very nice observation. Good reminder that sometimes you don't need to
> go fancy using different encodings and so on. Sometimes, changing a
> simple field value can make a difference (such as in this case). Many
> people have tried really hard to find XSS bugs in the main English
> version of the Google search page (there are several examples that
> went public), but this guy was much smarter and tried something
> different (changing the language parameter in this case).

Yesterday this worked for me and I disabled script for google.com .
Today I enabled the script for google and tested it again. I could not
reproduce it! Seems google has fixed this bug. Correct me if I'm
wrong. For now I have enabled script back for google.

Regards,

--
[vl@...ir]#