2 ms·
Shaders are the big vulnerability I know of. Any game developer will tell you: It's pretty easy to accidentally craft a shader that will totally stall particul
by snprbob86 15y ago
Shaders are the big vulnerability I know of.
Any game developer will tell you: It's pretty easy to accidentally craft a shader that will totally stall particular GPUs, taking down the entire windowing environment, if not the entire system. With malicious intent, shaders are a giant gaping DoS attack waiting to happen.
Beyond that, the shader compiler backends are supplied by third parties because they generate hardware specific opcodes and optimizations. Considering how poor nVidia and ATI's drivers have been historically, do you really trust them to create secure compilers?
In theory, Microsoft could implement a subset of WebGL without shaders, but I'd rather it not exist than be crippled and unusable. There are probably several other potential vulnerabilities I don't have firsthand experience with too.
All that said, I think that Java applets & JOGL already expose this attack vector.
- spullara 15y agoThose, like activex controls, require the user to agree to install something that can do whatever to their system. WebGL would be available to any web site.
- m_eiman 15y agoThat should be easy enough to duplicate, just make the feature one of those "Site X wants to use WebGL. [Allow] [Deny]" things. It would make it useless for ads and such, of course, but it seems that most people want to use it for games. Might be workable.
- nodata 15y agoThis is not a solution because a user would not know how to answer that question. We don't want ActiveX all over again. The solution is to address the problems in the article.