Changes

no edit summary
Line 18: Line 18:     
Well I have seen a Google Chrome exploit that uses a null pointer. It executes the nopsled and the shellcode so that it generates an exception.
 
Well I have seen a Google Chrome exploit that uses a null pointer. It executes the nopsled and the shellcode so that it generates an exception.
I think that if you try that exploit on Chrome on your computer, it still works(I tried it on version 15.0.865.1000, and it generated an exception. So I think that's a sign that Google and the Chromium team still haven't fixed the exploit yet, but my antivirus detects it). But what I said might be wrong and misleading. And sometimes null pointer dereferencing can be exploitable if you try and think harder.  --[[User:Kiddyshaq34|Kiddyshaq34]] 22:00, 03 September 2011 (GMT)
+
I think that if you try that exploit on Chrome on your computer, it still works(I tried it on version 15.0.865.1000 with sandbox disabled, and it generated an exception(a few times). So I think that's a sign that Google and the Chromium team still haven't fixed the exploit yet, but my antivirus detects it). But what I said might be wrong and misleading. And sometimes null pointer dereferencing can be exploitable if you try and think harder.  --[[User:Kiddyshaq34|Kiddyshaq34]] 22:00, 03 September 2011 (GMT)
     
19

edits