full-disclosure - Re: Apple Safari ... DoS 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] [day] [month] [year] [list]

Message-ID: <20090304032033.31F4.0@paddy.troja.mff.cuni.cz>
Date: Wed, 4 Mar 2009 03:51:25 +0100 (CET)
From: Pavel Kankovsky <peak@...o.troja.mff.cuni.cz>
To: full-disclosure <full-disclosure@...ts.grok.org.uk>
Subject: Re: Apple Safari ... DoS Vulnerability

On Mon, 2 Mar 2009, Chris Evans wrote:

> For the sake of prolonging a pointless argument, let's stick to the
> original premise of a tab crash with no other consequence, and see
> where it goes :)

It depends on where the piece of data causing the crash has come from.

(1) Could it (or any other piece of data in its place) make arbitrary
changes to the contents of the loaded page without having to rely on any
browser bug (e.g. the top HTML document)?

(2) Does it originate from the same subject (person, company, whatever)
as any other piece of data that is included in the loaded page and able
to make arbitrary changes as per (1)?

The crash is a real (DoS) attack against the browser if and only if
the answer to both questions is negative. (Assuming the crash has no
consequences other than the loss of the page loaded into the crashed
tab.)

-- 
Pavel Kankovsky aka Peak                          / Jeremiah 9:21        \
"For death is come up into our MS Windows(tm)..." \ 21th century edition /

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