879728 - webGL proxy/secure graphics

Status: RESOLVED INCOMPLETE

(Core :: Graphics: CanvasWebGL, defect, P3)

Description

[marta]

We need to ensure that the webGL is not abused for an unauthorised access to the phone.

Comment 1

[Jason Smith [:jsmith]]

I don't understand what this bug is about. There's no STR, no expected/actual results.

Comment 2

[Daniel Veditz [:dveditz]]

It doesn't sound like a specific vulnerability has been identified so I'm calling this a "security audit" bug.

If you don't want webGL abused you could always turn it off, but we haven't felt the need to do so on Desktop or Android. Is there a different set of worries on b2g?

Comment 3

[marta]

Sorry, maybe I was to brief on the bug description, as it follows a longer discussion I have had with Guillaume. 
There is a need for limiting the memory access that can be obtained by abusing the webGL and tricking the GPU into writing/reading to/from memory regions it is not supposed to access. 
I added the bug, as it was agreed that I will contribute in this area, and I couldn't find a bug entry in bugzilla. For now it is only listed here: https://wiki.mozilla.org/B2G/Architecture/System_Security#Road_Map (second after seccomp).

Comment 4

[Benoit Jacob [:bjacob] (mostly away)]

The WebGL implementation already guards against illegal memory accesses. Did you identify a specific area where the checks performed by the WebGL implementation are insufficient?

Comment 5

[Kelsey Gilbert [:jgilbert]]

We are tracking this elsewhere.