The malware is part of the popular BlackHole Exploit Kit and infects computers through vulnerabilities in Java and Adobe Reader, two third-party programs that basically everybody has on their computer. Kapersky reports that once Rootkit.Win64.Necurs.a gets its foot in the door, it starts downloading those annoying fake antivirus programs – you know, the “OMG! Your computer has umpteen million infected files! Click here to buy a fix!” type. The downloader gets around the Windows 64-bit protection by activating a driver test command that keeps PatchGuard from slamming on the brakes.

An interesting tidbit: one of the fake antiviruses the program tries to download is Hoax.OSX.Defma.f, a fake antivirus for Mac OS X. Obviously, it won’t work, being downloaded to a 64-bit Windows computer and all, but it points to an not-quite-so-obsure, post-Mac Defender future for Mac users.

Apparently so, as Context, a British security consultancy, released a security bulletin this week warning that the Web Graphics Library (WebGL) is vulnerable to denial of service (DoS) attacks and cross-domain image theft.

WebGL is a specification that allows Web browsers to use OpenGL–a 3-D, hardware-accelerated graphics API–with HTML5. WebGL is built into Firefox 4 and Chrome, and included with–but not enabled by default–in Safari. Many people see WebGL as a potential open source replacement for Flash, with some added benefits. Notably, WebGL is based on markup language, which means that unlike Flash, WebGL content can be indexed by search engines.

But WebGL can be compromised–causing graphics cards to lock up or execute arbitrary code–if it’s fed overly complex shading or rendering requests, or infinite-loop requests, according to Context. “It is easy to trivialize client denial of service attacks when the only affected component is the browser process–there are numerous ways of doing this already–however in this case the attack can completely prevent a user being able to access their computer, making it considerably more serious,” Context said.

Virtual desktop infrastructure is one of the hottest virtualization trends today. Buy why?
Review the major benefits of VDI now.

Results of a denial of service attack against WebGL include everything from making a computer unavailable to actually exploiting the machine. Context, however, declined to release related attack code.

Interestingly, the WebGL documentation itself contains a warning that the specification is subject to denial of service attacks: “It is possible to create, either intentionally or unintentionally, combinations of shaders and geometry that take an undesirably long time to render,” in effect shutting down the graphics card.

Likewise, the specification suggests a number of ways in which such attacks might be blocked, but punts solving the problem until later. “The supporting infrastructure at the OS and graphics API layer is expected to improve over time, which is why the exact nature of these safeguards is not specified,” it reads.

In response to Context’s security warning, the Khronos Group, which is the open standards consortium in charge of maintaining the WebGL specification, said that it’s already developed a WebGL extension called GL_ARB_robustness, “specifically designed to prevent denial of service and out-of-range memory access attacks from WebGL content.”

Khronos also is considering further measures, such as securing cross-domain images. “The ability to incorporate cross-domain images into WebGL scenes provides great utility to developers, but the WebGL working group is considering requiring cross-origin resource sharing (CORS) opt-in or other mechanisms to prevent abuse of this capability,” it said.

According to Context, the GL_ARB_robustness extension, which would be included by a graphics hardware manufacturer on their chips, “seems that it would at least mitigate the direct DoS condition where the whole machine becomes unresponsive or crashes.” But the extension would also require manufacturers to detect when machines lock up, and then react. That means that a graphics card could still lock up or at least interrupt users.

As a result, “we do not believe it addresses the wider issue,” according to a blog post from Context. “The resetting of the graphics card and driver should be seen as a crutch to OS stability when exceptional conditions occur and not as a mechanism to protect users from malicious code.”

Accordingly, Context recommends disabling WebGL until there’s a fix. The SANS Storm Center offers instructions for deactivating WebGL in both Firefox and Chrome.