So I remember sitting in a class in Graduate School talking about vulnerabilities via the Operating System when they started to theorize about exploits subverting using crazy methods like RAM and BIOS chips and graphics cards... weird how now all of these things have come to fruition.
Context IS wrote a blog about the vulnerabilities inherent in WebGL (Web Graphics Library) and what can be done with it. Basically WebGL allows for the rendering of 3D objects in the browser with Javascript. The issue is HOW it accomplishes this, digging into the GPU in the highly coveted and sacred kernel mode.
Khronos actually has a web page which is a PoC for causing a denial of service.CAUTION: This will probably crash your system. You have been warned.
Interestingly enough, another issue is the stealing of images. Context show a video of using the WebGL to basically scan an image line by line (its not that easy, but I am trying to get you to read their article), therefor ripping it from a site. I wonder if this could be used to snag those images used in mobile banking? How about 'watermarked' images?
Another indicator as to the potential danger of this, Microsoft does not seem to want to implement WebGL on IE (or at least by default as far as I can see) because of these very concerns. However, Chrome and Mozilla have it in their browsers.
It's crazy to think about all the ways a hacker can now pwn a system. My interest in this one is: what forensic artifacts (if any) would remain on the machine if this was used? Memory? Would we now have to somehow read the GPU to see what is in there?
An analysts job is never done.
1 comment:
I remember that class as well. Man, time has flown. How strange to come across you on the web as I peruse my daily reads (you were linked in Harlan's blog here http://windowsir.blogspot.com/2011/10/tools-and-links.html). It's good to see we're both continuing to use our education for good :)
Post a Comment