Issue metadata
Sign in to add a comment
|
heap-buffer-overflow-add_line and leads browser crash to aw,snap page
Reported by
rooterka...@gmail.com,
Sep 12 2017
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36 Steps to reproduce the problem: 1.open chrome 2. OPen the file Attached 3. it will crash the chrome and you can see the aw,snap Page What is the expected behavior? It should not crash. What went wrong? Attached file is causing heap overflow on browser but since i have office laptop i am not able to do further analysis. While testing bug of firefox i am able to reproduce this issue on chrome I am noob in browser fuzzing. SO sorry if i bother you again. But i thought i should report it as it is reproducible Did this work before? N/A Chrome version: 60.0.3112.113 Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 26.0 r0 I am noob in browser fuzzing. SO sorry if i bother you again. But i thought i should report it as it is reproducible and multiple failure can one day leads to success :)
,
Sep 12 2017
ClusterFuzz is analyzing your testcase. Developers can follow the progress at https://clusterfuzz.com/testcase?key=6372224008454144.
,
Sep 12 2017
This indeed looks like an out of memory case. OOMs are not security bugs, as the renderer can crash controllably so I'm closing this as WontFix. Please do let us know if we are missing anything.
,
Dec 20 2017
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by elawrence@chromium.org
, Sep 12 2017Status: Untriaged (was: Unconfirmed)