bugtraq - Re: [Full-disclosure] Firefox + popup blocker + XMLHttpRequest + srand() = oops

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]

Date: Mon, 5 Feb 2007 13:44:22 +0100 (CET)
From: Michal Zalewski <lcamtuf@...ne.ids.pl>
To: "pdp (architect)" <pdp.gnucitizen@...glemail.com>
Cc: bugtraq@...urityfocus.com, full-disclosure@...ts.grok.org.uk
Subject: Re: [Full-disclosure] Firefox + popup blocker + XMLHttpRequest +
 srand() = oops

On Mon, 5 Feb 2007, pdp (architect) wrote:

> You may as well use a QuickTime .mov/.qtl or a PDF document to open a
> file:// link . I think it is easier.

Sure. You can probably have a file:// link in Open Office / MS Office
documents as well; but these all rely on external components, and as such,
attacks could be shrugged off as a weakness in these apps (and there's
some truth to this).

Browser authors know better, and they disallow file:// URLs from the
Internet ever since Javascript became so powerful; this case managed to
slip through, so I thought it's a neat example, in conjunction with
deterministic temporary files.

/mz