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
Register for Dark Reading Newsletters
Dark Reading Live EVENTS
INsecurity - For the Defenders of Enterprise Security
A Dark Reading Conference
While red team conferences focus primarily on new vulnerabilities and security researchers, INsecurity puts security execution, protection, and operations center stage. The primary speakers will be CISOs and leaders in security defense; the blue team will be the focus.
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: " I think Google Doodle is getting a little out of control"
Current Issue
Security Vulnerabilities: The Next Wave
Just when you thought it was safe, researchers have unveiled a new round of IT security flaws. Is your enterprise ready?
Flash Poll
[Strategic Security Report] Assessing Cybersecurity Risk
[Strategic Security Report] Assessing Cybersecurity Risk
As cyber attackers become more sophisticated and enterprise defenses become more complex, many enterprises are faced with a complicated question: what is the risk of an IT security breach? This report delivers insight on how today's enterprises evaluate the risks they face. This report also offers a look at security professionals' concerns about a wide variety of threats, including cloud security, mobile security, and the Internet of Things.
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.