3 ms·

You seem to have entirely lost the context. We're talking what you can attack from code running on the GPU (aka, from a compute shader), which does not include

You seem to have entirely lost the context. We're talking what you can attack from code running on the GPU (aka, from a compute shader), which does not include the drivers since that's not running on the GPU. If you want to attack the shader compiler go for it, but since that lives in your own process anyway so you could skip that step and go straight to attacking whatever it is you wanted to attack. > WebGL history (it's been much worse, not DoS only etc). Such as? All I'm finding are DoS attacks. But regardless WebGL's problems were more due to WebGL and its designs than in vulnerabilities in the drivers or GPUs.

fulafel 9y ago
The context was "How do you prevent shaders being used to gain elevated privileges?" and those go through the whole stack. Regarding WebGL vulnerabilities, you can use your favourite search engine to look up vulnerabilities, here are some first hits for RCE bugs: https://www.cvedetails.com/cve/CVE-2012-3968/ https://www.cvedetails.com/cve/CVE-2012-3968/ https://bugs.chromium.org/p/chromium/issues/detail?id=740603 https://bugs.chromium.org/p/chromium/issues/detail?id=740603 https://nvd.nist.gov/vuln/detail/CVE-2017-5128 https://nvd.nist.gov/vuln/detail/CVE-2017-5128