Hacker News new | past | comments | ask | show | jobs | submit login

Just want to reply to say I also would like to hear an answer to this question. Something I've wanted to do for a while is write a fuzzer [1] that puts together arbitrary garbage shader script code and runs it with weird webgl operations looking for exploitable crashes. I would expect there to be a ton of bugs found, but then again the monetary barrier to entry might be high considering differences between hardware.

It also looks like the good folks at Mozilla have already been doing this to some degree [2], presumably shrinking the untested threat surface considerably (man I love those guys).

[1] http://en.wikipedia.org/wiki/Fuzz_testing

[2] https://bugzilla.mozilla.org/show_bug.cgi?id=665936




Here's a WebGL fuzzer from Mozilla bug 614678:

https://bug614678.bugzilla.mozilla.org/attachment.cgi?id=493...


> Just want to reply to say I also would like to hear an answer to this question.

The question is that they do what a business is required to do: let the market decide. Shockingly, the market does not want actual security; it wants lip service to make people feel safe and it wants shiny features.


This is happening and Google & Mozilla have both been dealing out bug bounties for vulnerabilities found this way.

You can search for them in eg chrome bug db: https://encrypted.google.com/search?hl=en&q=site%3Acode.goog...

(this shows just the subset they've remembered to make public, some time after fixes were shipping in stable)


It would be an interesting project. You should go ahead and test the current implementations! Actually, would you even need webgl to hunt for GLSL exploits?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: