New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 603518 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Apr 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 1
Type: Bug-Security



Sign in to add a comment

Security: PDFium Out-of-Bounds Read in CPDF_DeviceCS::TranslateImageLine

Reported by stackexp...@gmail.com, Apr 14 2016

Issue description

VULNERABILITY DETAILS
The attached proof-of-concept file could crash the latest build of pdfium_test.
This is an Out-Of-Bounds Read issue.
The exception information is presented as follows.

-----------------------
Exception Information
-----------------------
(35a8.3bc8): Access violation - code c0000005 (!!! second chance !!!)
eax=003cf532 ebx=003cf531 ecx=01248fc8 edx=014c8ff0 esi=00000000 edi=07e7bffe
eip=0137f5bf esp=003cf4c4 ebp=003cf4e0 iopl=0         nv up ei pl zr na pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
pdfium_test!CPDF_DeviceCS::TranslateImageLine+0x15f:
0137f5bf 0fb64702        movzx   eax,byte ptr [edi+2]       ds:002b:07e7c000=??

-----------------------
Stack Trace Information
-----------------------
pdfium_test!CPDF_DeviceCS::TranslateImageLine+0x15f [pdfium\core\fpdfapi\fpdf_page\fpdf_page_colors.cpp @ 205]
pdfium_test!CPDF_DIBSource::DownSampleScanline32Bit+0x2a1 [pdfium\core\fpdfapi\fpdf_render\fpdf_render_loadimage.cpp @ 1428]
pdfium_test!CPDF_DIBSource::DownSampleScanline+0x19a [pdfium\core\fpdfapi\fpdf_render\fpdf_render_loadimage.cpp @ 1223]
pdfium_test!CFX_ImageStretcher::ContinueQuickStretch+0xa8 [pdfium\core\fxge\dib\fx_dib_engine.cpp @ 909]
pdfium_test!CFX_ImageRenderer::Continue+0x1c [pdfium\core\fxge\dib\fx_dib_main.cpp @ 1674]
pdfium_test!CFX_AggDeviceDriver::ContinueDIBits+0x23 [pdfium\core\fxge\agg\fx_agg_driver.cpp @ 1789]
pdfium_test!CPDF_ImageRenderer::Continue+0xf9 [pdfium\core\fpdfapi\fpdf_render\fpdf_render_image.cpp @ 857]
pdfium_test!CPDF_RenderStatus::ContinueSingleObject+0xd3 [pdfium\core\fpdfapi\fpdf_render\fpdf_render.cpp @ 309]
pdfium_test!CPDF_ProgressiveRenderer::Continue+0x2de [pdfium\core\fpdfapi\fpdf_render\fpdf_render.cpp @ 1103]
pdfium_test!FPDF_RenderPage_Retail+0x221 [pdfium\fpdfsdk\fpdfview.cpp @ 936]
pdfium_test!FPDF_RenderPageBitmap+0x99 [pdfium\fpdfsdk\fpdfview.cpp @ 668]
pdfium_test!RenderPage+0x1b8 [pdfium\samples\pdfium_test.cc @ 450]
pdfium_test!RenderPdf+0x2ef [pdfium\samples\pdfium_test.cc @ 626]
pdfium_test!main+0x2e6 [pdfium\samples\pdfium_test.cc @ 749]
pdfium_test!invoke_main+0x1d [f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl @ 74]
pdfium_test!__scrt_common_main_seh+0xff [f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl @ 264]
kernel32!BaseThreadInitThunk+0xe
ntdll!__RtlUserThreadStart+0x70
ntdll!_RtlUserThreadStart+0x1b

-----------------------
Vulnerability Analysis
-----------------------
0:000> !heap -p -a edi
    address 07e7bffe found in
    _DPH_HEAP_ROOT @ 1d1000
    in busy allocation (  DPH_HEAP_BLOCK:  UserAddr  UserSize - VirtAddr  VirtSize)
                                 7e22bfc:   7e7b880       780 -  7e7b000      2000
    72c88e89 verifier!AVrfDebugPageHeapAllocate+0x00000229
    76f91d4e ntdll!RtlDebugAllocateHeap+0x00000030
    76f4b586 ntdll!RtlpAllocateHeap+0x000000c4
    76ef3541 ntdll!RtlAllocateHeap+0x0000023a
    0146f119 pdfium_test!_calloc_base+0x00000047 [d:\th\minkernel\crts\ucrt\src\appcrt\heap\calloc_base.cpp @ 33]
    013aa67a pdfium_test!CCodec_JpegDecoder::Create+0x0000011a [pdfium\core\fxcodec\codec\fx_codec_jpeg.cpp @ 435]
    013aa707 pdfium_test!CCodec_JpegModule::CreateDecoder+0x00000047 [pdfium\core\fxcodec\codec\fx_codec_jpeg.cpp @ 490]
    01391dba pdfium_test!CPDF_DIBSource::CreateDecoder+0x000001ba [pdfium\core\fpdfapi\fpdf_render\fpdf_render_loadimage.cpp @ 587]
    0139427b pdfium_test!CPDF_DIBSource::StartLoadDIBSource+0x0000015b [pdfium\core\fpdfapi\fpdf_render\fpdf_render_loadimage.cpp @ 312]
    0137c8d7 pdfium_test!CPDF_ImageCacheEntry::StartGetCachedBitmap+0x00000067 [pdfium\core\fpdfapi\fpdf_render\fpdf_render_cache.cpp @ 278]
    0137c9df pdfium_test!CPDF_PageRenderCache::StartGetCachedBitmap+0x000000cf [pdfium\core\fpdfapi\fpdf_render\fpdf_render_cache.cpp @ 125]
    01394084 pdfium_test!CPDF_ImageLoaderHandle::Start+0x00000044 [pdfium\core\fpdfapi\fpdf_render\fpdf_render_loadimage.cpp @ 1504]
    0139402d pdfium_test!CPDF_ImageLoader::Start+0x0000005d [pdfium\core\fpdfapi\fpdf_render\fpdf_render_loadimage.cpp @ 1565]
    01373400 pdfium_test!CPDF_ImageRenderer::StartLoadDIBSource+0x00000070 [pdfium\core\fpdfapi\fpdf_render\fpdf_render_image.cpp @ 343]
    01372e74 pdfium_test!CPDF_ImageRenderer::Start+0x00000074 [pdfium\core\fpdfapi\fpdf_render\fpdf_render_image.cpp @ 487]
    01354ef4 pdfium_test!CPDF_RenderStatus::ContinueSingleObject+0x000000b4 [pdfium\core\fpdfapi\fpdf_render\fpdf_render.cpp @ 330]
    01354d1e pdfium_test!CPDF_ProgressiveRenderer::Continue+0x000002de [pdfium\core\fpdfapi\fpdf_render\fpdf_render.cpp @ 1103]
    01329591 pdfium_test!FPDF_RenderPage_Retail+0x00000221 [pdfium\fpdfsdk\fpdfview.cpp @ 936]
    01329e39 pdfium_test!FPDF_RenderPageBitmap+0x00000099 [pdfium\fpdfsdk\fpdfview.cpp @ 668]
    01323168 pdfium_test!RenderPage+0x000001b8 [pdfium\samples\pdfium_test.cc @ 450]
    0132355f pdfium_test!RenderPdf+0x000002ef [pdfium\samples\pdfium_test.cc @ 626]
    01328766 pdfium_test!main+0x000002e6 [pdfium\samples\pdfium_test.cc @ 749]
    01461ebd pdfium_test!__scrt_common_main_seh+0x000000ff [f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl @ 264]
    7647338a kernel32!BaseThreadInitThunk+0x0000000e
    76ef9a02 ntdll!__RtlUserThreadStart+0x00000070
    76ef99d5 ntdll!_RtlUserThreadStart+0x0000001b

0:000> ?7e7b880 + 780
Evaluate expression: 132628480 = 07e7c000

0:000> r
eax=003cf532 ebx=003cf531 ecx=01248fc8 edx=014c8ff0 esi=00000000 edi=07e7bffe
eip=0137f5bf esp=003cf4c4 ebp=003cf4e0 iopl=0         nv up ei pl zr na pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
pdfium_test!CPDF_DeviceCS::TranslateImageLine+0x15f:
0137f5bf 0fb64702        movzx   eax,byte ptr [edi+2]     ds:002b:07e7c000=??

Here 07e7c000 is greater than the upper bounds of the heap. It will cause a heap based out-of-bounds read issue.

-----------------------
Credit
-----------------------
This vulnerability was discovered by Ke Liu of Tencent's Xuanwu LAB (http://www.tencent.com/).


VERSION
Chrome Version: [x.x.x.x] + [stable, beta, or dev]
PDFium Version: latest version built with Visual Studio 2015, both xfa and javascript were disabled.
Operating System: [Windows 7 SP1]

REPRODUCTION CASE
This issue was caused by the malformed JPEG image embedded in the PDF document.
The malformed jpeg, the malformed pdf, and the normal jpeg were all attached.

FOR CRASHES, PLEASE INCLUDE THE FOLLOWING ADDITIONAL INFORMATION
See at section VULNERABILITY DETAILS.

 
------------------------
Additionally Analysis
------------------------
(28d8.2164): Access violation - code c0000005 (!!! second chance !!!)
eax=0027f48e ebx=0027f48d ecx=07558fc8 edx=014e8ff0 esi=00000000 edi=07f3cffe
eip=0139f5bf esp=0027f420 ebp=0027f43c iopl=0         nv up ei pl zr na pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
pdfium_test!CPDF_DeviceCS::TranslateImageLine+0x15f:
0139f5bf 0fb64702        movzx   eax,byte ptr [edi+2]     ds:002b:07f3d000=??

$$ local variables
0:000> dv
           this = 0x07558fc8
       pDestBuf = 0x0027f48c "!!&???"
        pSrcBuf = 0x07f3cffd "???"        <-------------------- ①
         pixels = 0n1
    image_width = 0n0
   image_height = 0n0
     bTransMask = 0n0
              k = <value unavailable>
              i = <value unavailable>
              
0:000> r edi
edi=07f3cffe                              <-------------------- ②

$$ we can conclude that pSrcBuf=edi-1 according to ① & ②.

0:000> u eip
pdfium_test!CPDF_DeviceCS::TranslateImageLine+0x15f [pdfium\core\fpdfapi\fpdf_page\fpdf_page_colors.cpp @ 205]:
0139f5bf 0fb64702        movzx   eax,byte ptr [edi+2]       ; pSrcBuf[3], oob access
0139f5c3 50              push    eax
0139f5c4 0fb64701        movzx   eax,byte ptr [edi+1]       ; pSrcBuf[2]
0139f5c8 50              push    eax
0139f5c9 0fb607          movzx   eax,byte ptr [edi]         ; pSrcBuf[1]
0139f5cc 50              push    eax
0139f5cd 0fb647ff        movzx   eax,byte ptr [edi-1]       ; pSrcBuf[0]
0139f5d1 50              push    eax

$$ we can see that only two bytes were available at the tail of the heap.
0:000> db edi
07f3cffe  ad a7 ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ..??????????????
07f3d00e  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????
07f3d01e  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????
07f3d02e  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????
07f3d03e  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????
07f3d04e  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????
07f3d05e  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????
07f3d06e  ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??  ????????????????

------------------------
Source Code
------------------------
177  void CPDF_DeviceCS::TranslateImageLine(uint8_t* pDestBuf,
178                                         const uint8_t* pSrcBuf,
179                                         int pixels,
180                                         int image_width,
181                                         int image_height,
182                                         FX_BOOL bTransMask) const {
183    if (bTransMask && m_Family == PDFCS_DEVICECMYK) {
184      for (int i = 0; i < pixels; i++) {
185        int k = 255 - pSrcBuf[3];
186        pDestBuf[0] = ((255 - pSrcBuf[0]) * k) / 255;
187        pDestBuf[1] = ((255 - pSrcBuf[1]) * k) / 255;
188        pDestBuf[2] = ((255 - pSrcBuf[2]) * k) / 255;
189        pDestBuf += 3;
190        pSrcBuf += 4;
191      }
192      return;
193    }
194    if (m_Family == PDFCS_DEVICERGB) {
195      ReverseRGB(pDestBuf, pSrcBuf, pixels);
196    } else if (m_Family == PDFCS_DEVICEGRAY) {
197      for (int i = 0; i < pixels; i++) {
198        *pDestBuf++ = pSrcBuf[i];
199        *pDestBuf++ = pSrcBuf[i];
200        *pDestBuf++ = pSrcBuf[i];
201      }
202    } else {
203      for (int i = 0; i < pixels; i++) {
204        if (!m_dwStdConversion) {                                             // ------------------------------------
205          AdobeCMYK_to_sRGB1(pSrcBuf[0], pSrcBuf[1], pSrcBuf[2], pSrcBuf[3],  // Here pSrcBuf[3] caused an oob access
206                             pDestBuf[2], pDestBuf[1], pDestBuf[0]);          // ------------------------------------
207        } else {
208          uint8_t k = pSrcBuf[3];
209          pDestBuf[2] = 255 - std::min(255, pSrcBuf[0] + k);
210          pDestBuf[1] = 255 - std::min(255, pSrcBuf[1] + k);
211          pDestBuf[0] = 255 - std::min(255, pSrcBuf[2] + k);
212        }
213        pSrcBuf += 4;
214        pDestBuf += 3;
215      }
216    }

------------------------
Affected Version
------------------------
Latest version of pdfium is vulnerable (https://pdfium.googlesource.com/pdfium/+/bd9748d504555f100d34025d76a9e0119986bc3f).
------------------------
diff
------------------------
There are 4 bytes of difference. 

The first two bytes are located at sof0.
struct sof0 {
    marker      FF C0
    section     00 11
    precision   08
    Y_image     F9 10       // changed from [01 E0]
    X_image     02 80
    nr_comp     03
    comp[0]     01 11 00
    comp[1]     02 11 01
    comp[2]     03 11 01
}

The second two bytes are located at DHT.
struct DHT {
    marker      FF C4
    section     00 75  // changed from [00 74]
    
    huff_table[0]
        info    00
        length  01 01 01 01 01 01 01 00 00 00 00 00 00 00 00 00
        HTV     00 01 02 03 04 05 07
        
    huff_table[1]
        info    01
        length  [01] 01 01 01 01 01 00 00 00 00 00 00 00 00 00 00 // the first byte was extra inserted
        HTV     00 00 01 02 03 07
        
    ......
}
Here the structure of the DHT section was corrupted.

Comment 3 by tsepez@chromium.org, Apr 14 2016

Components: Internals>Plugins>PDF
Labels: Security_Severity-Medium M-51 Security_Impact-Stable OS-All Pri-2
Owner: och...@chromium.org
Status: Assigned (was: Unconfirmed)
@ochang, is this something we've seen before?  Thanks.
Project Member

Comment 4 by ClusterFuzz, Apr 14 2016

ClusterFuzz is analyzing your testcase. Developers can follow the progress at https://cluster-fuzz.appspot.com/testcase?key=4963126709059584
Project Member

Comment 5 by ClusterFuzz, Apr 14 2016

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=4963126709059584

Uploader: ochang@google.com
Job Type: linux_asan_pdfium
Platform Id: linux

Crash Type: Heap-buffer-overflow READ 1
Crash Address: 0x61c00000e800
Crash State:
  CPDF_DeviceCS::TranslateImageLine
  CPDF_DIBSource::DownSampleScanline32Bit
  CPDF_DIBSource::DownSampleScanline
  
Recommended Security Severity: Medium

Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_pdfium&range=289356:289512

Minimized Testcase (7.16 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94qS1ax0v2N44qRWnLdfMR7OiFlzNJo9HSjQLhQiPHT7t69Bm2FVOpVhPdYNwMc65bPqWUllvb4EdfJ6Q4hC_Uo2PCbcYZaZ92wSC0c6_RSicfzt49xyA3cMmEa3z2SX4YlhUvtSKw6q2xp3W7xgI5OEjA42Q

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
Project Member

Comment 6 by ClusterFuzz, Apr 14 2016

Labels: -Pri-2 Pri-1
Is it similar to this issue?
https://bugs.chromium.org/p/chromium/issues/detail?id=382820
Project Member

Comment 8 by bugdroid1@chromium.org, Apr 15 2016

The following revision refers to this bug:
  https://pdfium.googlesource.com/pdfium.git/+/7cf555202756c51ce2b5ae18efdeb6e1bb6a9e41

commit 7cf555202756c51ce2b5ae18efdeb6e1bb6a9e41
Author: ochang <ochang@chromium.org>
Date: Fri Apr 15 20:52:00 2016

Prevent a potential OOB read in TranslateImageLine.

Fixes a potential mismatch of |m_nComponents| between CPDF_DIBSource and
its CPDF_ColorSpace, from code attempting to recover from a failed decoder
initialisation in CPDF_DIBSource::CreateDecoder.

BUG= chromium:603518 
R=tsepez@chromium.org

Review URL: https://codereview.chromium.org/1892143003

[modify] https://crrev.com/7cf555202756c51ce2b5ae18efdeb6e1bb6a9e41/core/fpdfapi/fpdf_render/fpdf_render_loadimage.cpp
[modify] https://crrev.com/7cf555202756c51ce2b5ae18efdeb6e1bb6a9e41/core/fpdfapi/fpdf_render/fpdf_render_loadimage_embeddertest.cpp
[add] https://crrev.com/7cf555202756c51ce2b5ae18efdeb6e1bb6a9e41/testing/resources/bug_603518.pdf

Project Member

Comment 9 by bugdroid1@chromium.org, Apr 15 2016

Labels: Merge-Request-51
Status: Fixed (was: Assigned)

Comment 11 by tin...@google.com, Apr 18 2016

Labels: -Merge-Request-51 Merge-Review-51 Hotlist-Merge-Review
[Automated comment] DEPS changes referenced in bugdroid comments, needs manual review.
Project Member

Comment 12 by ClusterFuzz, Apr 18 2016

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=4963126709059584

Uploader: ochang@google.com
Job Type: linux_asan_pdfium
Platform Id: linux

Crash Type: Heap-buffer-overflow READ 1
Crash Address: 0x61c00000e800
Crash State:
  CPDF_DeviceCS::TranslateImageLine
  CPDF_DIBSource::DownSampleScanline32Bit
  CPDF_DIBSource::DownSampleScanline
  
Recommended Security Severity: Medium

Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_pdfium&range=289356:289512

Minimized Testcase (7.16 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94qS1ax0v2N44qRWnLdfMR7OiFlzNJo9HSjQLhQiPHT7t69Bm2FVOpVhPdYNwMc65bPqWUllvb4EdfJ6Q4hC_Uo2PCbcYZaZ92wSC0c6_RSicfzt49xyA3cMmEa3z2SX4YlhUvtSKw6q2xp3W7xgI5OEjA42Q

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
Labels: -Merge-Review-51 Merge-Approved-51
Merge approved for M51 (branch 2704)
Please merge your change to M51 branch 2704 ASAP (before 6:00 PM PST, today) so we can take it in for M51 last Dev release tomorrow.
Project Member

Comment 15 by bugdroid1@chromium.org, Apr 18 2016

Labels: -merge-approved-51 merge-merged-2704
The following revision refers to this bug:
  http://goto.ext.google.com/viewvc/chrome-internal?view=rev&revision=86732

------------------------------------------------------------------
r86732 | ochang@google.com | 2016-04-18T19:53:43.499907Z

-----------------------------------------------------------------
Project Member

Comment 16 by ClusterFuzz, Apr 18 2016

Labels: -Restrict-View-SecurityTeam Restrict-View-SecurityNotify
Project Member

Comment 17 by ClusterFuzz, Apr 19 2016

ClusterFuzz has detected this issue as fixed in range 387601:387928.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=4963126709059584

Uploader: ochang@google.com
Job Type: linux_asan_pdfium
Platform Id: linux

Crash Type: Heap-buffer-overflow READ 1
Crash Address: 0x61c00000e800
Crash State:
  CPDF_DeviceCS::TranslateImageLine
  CPDF_DIBSource::DownSampleScanline32Bit
  CPDF_DIBSource::DownSampleScanline
  
Recommended Security Severity: Medium

Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_pdfium&range=289356:289512
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_pdfium&range=387601:387928

Minimized Testcase (7.16 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94qS1ax0v2N44qRWnLdfMR7OiFlzNJo9HSjQLhQiPHT7t69Bm2FVOpVhPdYNwMc65bPqWUllvb4EdfJ6Q4hC_Uo2PCbcYZaZ92wSC0c6_RSicfzt49xyA3cMmEa3z2SX4YlhUvtSKw6q2xp3W7xgI5OEjA42Q

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Cc: timwillis@chromium.org
Labels: reward-topanel Release-0-M51
Thanks for the great report! We'll consider this under our Chrome security reward program: https://www.google.com/about/appsecurity/chrome-rewards/ and update you with a decision soon.
Labels: -reward-topanel CVE-2016-1686 reward-1000 reward-unpaid
Our reward panel decided to award you $1,000 for this report. Congratulations!

We've credited you in our release notes as "Ke Liu of Tencent's Xuanwu LAB": https://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html

Someone from our finance team will be in contact to collect details for payment within 7 days. If that doesn't happen, please either update this bug or contact me at timwillis@.

The CVE-ID for this issue is CVE-2016-1686. Usual boilerplate text below - let me know if you have any questions.

Thanks again for the report!


*** Boilerplate reminders! ***
Please do NOT publicly disclose details until a fix has been released to all our users. Early public disclosure may cancel the provisional reward. Also, please be considerate about disclosure when the bug affects a core library that may be used by other products. Please do NOT share this information with third parties who are not directly involved in fixing the bug. Doing so may cancel the provisional reward. Please be honest if you have already disclosed anything publicly or to third parties. Lastly, we understand that some of you are not interested in money. We offer the option to donate your reward to an established charity. If you prefer this option, let us know and we will also match your donation - subject to our discretion. Any rewards that are unclaimed after 12 months will be donated to a charity of our choosing.
Hi Timwillis, no one has contacted me so far.
Thanks for letting me know - I'll chase today along with  Issue 601362 .
Labels: -reward-unpaid reward-inprocess
Project Member

Comment 23 by sheriffbot@chromium.org, Jul 26 2016

Labels: -Restrict-View-SecurityNotify
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
Project Member

Comment 24 by sheriffbot@chromium.org, Oct 1 2016

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
Project Member

Comment 25 by sheriffbot@chromium.org, Oct 2 2016

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
Labels: allpublic
Labels: CVE_description-submitted

Sign in to add a comment