full-disclosure - Re: Google is vulnerable from XSS attack

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: <4b6ee9310512070955j2c0d728bo699a012a9ec952b5@mail.gmail.com>
Date: Wed Dec  7 17:55:41 2005
From: xploitable at gmail.com (n3td3v)
Subject: Re: Google is vulnerable from XSS attack

On 12/7/05, jpierini <jpierini@...mail.com> wrote:

"I'm just a CISSP, and as discussed numerous times I'm without the elite mad
skills of a hacker (XSS wasn't even on our test!)"

You're not a professional then in my eyes and don't have a right to be
even in this thread let alone go around wtih your CISSP title.

"Why won't the hacking community give the
vendors a reasonable amount of time to cover their asses"

Because Google took less than 48-hours to fix a less severe XSS flaw
the last time: http://www.zone-h.org/en/news/read/id=4439/

As a owner of a Google Group, I would personally like this patched for
the security of my group and that of my personal computer and web
browser.

"the damage is done"

Not yet, the longer Google leave it the more likely an attack on all
groups could be carried out.