3 ms·

Are there examples where this model has been abused to steal real data?

• jsheard 9y ago
  In the early days of WebGL some browsers leaked information via uninitialized GPU memory, so an attacker could potentially read texture data left behind by other processes. Todays WebGL implementations take care to wipe new memory allocations with zeros before letting the untrusted script do anything with them though.
  • FraKtus 9y ago
    That's the same than starting a process and mallocing some memory; you will have the garbage of the previous process... Because you have no idea who owned that memory and what it was used to it would be hard to build something on top of that. This being said it's not a bad idea to zero stuff when you start to use them.
• jburgess777 9y ago
  A long time ago, a bug in Firefox let a screenshot be taken of data outside the browser window: "This issue allows attackers to capture screen shots of private or confidential information" https://blog.mozilla.org/security/2011/06/16/webgl-graphics-memory-stealing-issue/ https://blog.mozilla.org/security/2011/06/16/webgl-graphics-...
  • FraKtus 9y ago
    I suppose this is more about reading another texture than the one you are supposed to use. GPU memory is flat, and there is no concept of process memory up there.