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: Apr 2015
Cc:



Sign in to add a comment
Flash: memory corruption with excessive dimensions in H264
Reported by cevans@google.com, Feb 25 2015 Back to list
To reproduce, host the attached SWF and other files on a web server (e.g. localhost) and load it like this:

http://localhost/PlayManifest.swf?file=h264wh.mp4

This particular example likes to die on out-of-memory on 32-bit Chrome, but use a 64-bit version and you'll probably get a memory corruption crash in memset().

A more convincing example could be constructed but this example goes for simplicity, it sets the picture width to 4096x4096 blocks, which is 65536x65536 pixels. The video file is based on a real file downloaded from the web, with the following differences (cmp -l format):

   4798 251 374
   4799  30   0
   4800  74  40
   4801  27   0
   4802 374   0
   4803 270  20
   4804   3   0
   4805 120 377


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.

 
LoadMP4.swf
1.0 KB Download
h264wh.mp4
1.1 MB Download
LoadMP4.as
1.0 KB Download
Comment 1 by cevans@google.com, Mar 3 2015
Labels: Id-3334
Comment 2 by cevans@google.com, Mar 3 2015
Correction: URL is:

http://localhost/LoadMP4.swf?file=h264wh.mp4
Comment 3 by cevans@google.com, Apr 10 2015
Labels: CVE-2015-0352
Comment 5 by cevans@google.com, Apr 30 2015
Labels: -Restrict-View-Commit
Sign in to add a comment