New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 2 users
Status: Fixed
Owner:
Email to this user bounced
Closed: Jun 2015
Cc:



Sign in to add a comment
Flash: uninitialized memory information leak when shading into a ByteArray (#2)
Reported by cevans@google.com, May 12 2015 Back to list
A PoC (source and SWF) are attached, along with a screenshot of the rendering of the uninitialized content into a Bitmap.

Sometimes, the PoC will render just a black image. To get things a bit more leaky, I found that playing a Flash video in a second tab whilst refreshing the PoC seems to do the trick reliably.

Unfortunately, this appears to be an incorrect fix for https://code.google.com/p/google-security-research/issues/detail?id=319.  Bug 319  used a zero mask to cause uninitialized memory, and that PoC does seem to be fixed. This latest PoC uses a non-zero but non-complete mask to achieve a similar affect.


This bug is subject to a 90 day disclosure deadline. If 90 days elapse
without a broadly available patch, then the bug report will automatically
become visible to the public.

 
shaderjobleak2.png
29.7 KB View Download
ShaderJobLeak2.swf
994 bytes Download
ShaderJobLeak2.as
1.3 KB Download
Comment 1 by cevans@google.com, May 12 2015
Labels: Id-3674
Comment 2 by cevans@google.com, Jun 4 2015
Labels: CVE-2015-3108
Comment 4 by cevans@google.com, Jun 26 2015
Labels: Fixed-2015-Jun-9
Comment 5 by cevans@google.com, Jun 26 2015
Labels: -Restrict-View-Commit
Sign in to add a comment