Linked by Thom Holwerda on Tue 22nd May 2012 23:26 UTC
Internet & Networking "Just over two months ago, Chrome sponsored the Pwnium browser hacking competition. We had two fantastic submissions, and successfully blocked both exploits within 24 hours of their unveiling. Today, we'd like to offer an inside look into the exploit submitted by Pinkie Pie." A work of pure art, this. Also, this is not the same person as the other PinkiePie. Also also, you didn't think I'd let a story with a headline like this go by unnoticed, did you?
Thread beginning with comment 519093
To read all comments associated with this story, please click here.
Comment by Radio
by Radio on Wed 23rd May 2012 06:42 UTC
Radio
Member since:
2009-06-20

Also also, you didn't think I'd let a story with a headline like this go by unnoticed, did you?

Red paint, girlscout, etc?

More seriously, the GPU is *again* the weak link. That is cause for concern for the security of modern browsers: is it manageable when they have so much code touching so many hard/soft wares?

Reply Score: 5

RE: Comment by Radio
by moondevil on Wed 23rd May 2012 07:47 in reply to "Comment by Radio"
moondevil Member since:
2005-07-08

Actually C and C++ are the weakest links, not the GPU, as the exploits take advantage of the pointer tricks so dear to C and C++ developers.

If ComputeMaxResults() was done in a more sane language, this exploit wouldn't have been possible, without doing some Assembly code rewriting.

Reply Parent Score: 1

RE[2]: Comment by Radio
by kwan_e on Wed 23rd May 2012 08:14 in reply to "RE: Comment by Radio"
kwan_e Member since:
2007-02-18

If ComputeMaxResults() was done in a more sane language, this exploit wouldn't have been possible, without doing some Assembly code rewriting.


Did you actually read the functions? It is a calculation logic error. There is no language alive to prevent logic errors. The logic error results in an invalid buffer access for a GPU related task. No "sane" language has yet been extended to use GPUs that do no rely on creating buffers directly at some point in its execution.

You do understand that were a managed language required to access the GPU, it would also need to do manual memory management undercovers, don't you?

Reply Parent Score: 6

RE: Comment by Radio
by renox on Wed 23rd May 2012 07:59 in reply to "Comment by Radio"
renox Member since:
2005-07-06

More seriously, the GPU is *again* the weak link. That is cause for concern for the security of modern browsers: is it manageable when they have so much code touching so many hard/soft wares?


And it's only a start: when I read about Firefox's developpers working on WebGL, I immediately thought: this feature has a lot of potential security issues..

Reply Parent Score: 2