Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

7/8/2011
05:54 PM
Connect Directly
Google+
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Google Implements WebGL Security Fix

Web developers wishing to make use of cross-domain media elements with WebGL should look to a new mechanism called CORS.

Google this week said that a security enhancement in the WebGL specification has limited the use of cross-domain image or video elements as WebGL textures in Chrome 13, and encouraged developers to utilize a specification known as CORS.

The explanatory post to the Chromium blog confirms what Google software engineer Kenneth Russell said about Chrome 13 in a mailing list message last month.

Chrome 13 is currently available to those subscribed to Google's beta channel; Chrome 12 is the stable release.

Microsoft last month took the unusual step of publicly condemning WebGL, an open alternative to its Windows DirectX graphics API, because of what it saw as potential security problems. "In its current form, WebGL is not a technology Microsoft can endorse from a security perspective," the company said, in a blog post titled "WebGL Considered Harmful."

The WebGL specification has since been revised to disallow the use of cross-domain media.

WebGL provides hardware-accelerated 3-D graphics in the browser without a plug-in. It is a critical component to browser makers aiming to support entertainment and graphics applications that compete with the sophisticated graphics capabilities of desktop apps. Google currently hosts an online showcase to illustrate the potential of the technology.

A spokesperson from The Khronos Group, which published the WebGL 1.0 specification in March, said last month that browser vendors are still working to make their WebGL implementations conform with the specification.

The group's spokesperson also addressed Microsoft's concern about denial-of-service attacks that could arise from shaders and geometry designed to crash graphics hardware.

"Browser vendors are still in the process of supporting the GL_ARB_robustness extension, so it is expected that the previously reported denial-of-service issues are still present," Khronos' spokesperson said. "It is expected that the reported denial-of-service issues will be solved with the integration of this extension."

Even as the WebGL security issues get ironed out, the changes in Chrome 13 have not completely eliminated the possibility of utilizing cross-domain media elements. Assuming the hosting image server allows it, a Web developer can employ a specification known as CORS (Cross-Origin Resource Sharing) to present images and videos that come from other domains.

"Unfortunately, this new restriction in WebGL means that some existing content will break," explained Google developer advocate Eric Bidelman in a blog post. "We've already started working with external image and video hosting services like Flickr to evangelize the use of CORS on their images."

Picasa, Google's online image service, already supports CORS.

In the new, all-digital Dark Reading supplement: What industry can teach government about IT innovation and efficiency. Also in this issue: Federal agencies have to shift from annual IT security assessments to continuous monitoring of their risks. Download it now. (Free registration required.)

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Data Leak Week: Billions of Sensitive Files Exposed Online
Kelly Jackson Higgins, Executive Editor at Dark Reading,  12/10/2019
Intel Issues Fix for 'Plundervolt' SGX Flaw
Kelly Jackson Higgins, Executive Editor at Dark Reading,  12/11/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-5252
PUBLISHED: 2019-12-14
There is an improper authentication vulnerability in Huawei smartphones (Y9, Honor 8X, Honor 9 Lite, Honor 9i, Y6 Pro). The applock does not perform a sufficient authentication in a rare condition. Successful exploit could allow the attacker to use the application locked by applock in an instant.
CVE-2019-5235
PUBLISHED: 2019-12-14
Some Huawei smart phones have a null pointer dereference vulnerability. An attacker crafts specific packets and sends to the affected product to exploit this vulnerability. Successful exploitation may cause the affected phone to be abnormal.
CVE-2019-5264
PUBLISHED: 2019-12-13
There is an information disclosure vulnerability in certain Huawei smartphones (Mate 10;Mate 10 Pro;Honor V10;Changxiang 7S;P-smart;Changxiang 8 Plus;Y9 2018;Honor 9 Lite;Honor 9i;Mate 9). The software does not properly handle certain information of applications locked by applock in a rare condition...
CVE-2019-5277
PUBLISHED: 2019-12-13
Huawei CloudUSM-EUA V600R006C10;V600R019C00 have an information leak vulnerability. Due to improper configuration, the attacker may cause information leak by successful exploitation.
CVE-2019-5254
PUBLISHED: 2019-12-13
Certain Huawei products (AP2000;IPS Module;NGFW Module;NIP6300;NIP6600;NIP6800;S5700;SVN5600;SVN5800;SVN5800-C;SeMG9811;Secospace AntiDDoS8000;Secospace USG6300;Secospace USG6500;Secospace USG6600;USG6000V;eSpace U1981) have an out-of-bounds read vulnerability. An attacker who logs in to the board m...