Author: Dan Sinclair
Project: chromium-pdfium
Changelist: https://pdfium.googlesource.com/pdfium.git/+/764ec513eecbebd12781bcc96ce81ed5e736ee92
Time: Mon Mar 14 13:35:12 2016 -0400
The CL last changed line 285 of file fx_dib_engine.cpp, which is stack frame 0.

@dsinclair: Assigning to you, request you to please take a look into it. Please help us to reassign if not with respect to your change.

Thanks.!

Looks like find-it is wrong. The blamed CL just moves code around. Can we please re-run find-it?

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Author: thestig
Project: chromium-pdfium
Changelist: https://pdfium.googlesource.com/pdfium.git/+/9febfe6373f26d9e59eb1e137b88a2aeff5dc39a
Time: Wed May 11 18:31:20 2016 -0700
The CL last changed line 855 of file fx_dib_engine.cpp, which is stack frame 1.

@thestig: CC'ing you, request you to please take a look into it. Please help us to find an owner if not with respect to your change.

Thanks.!

ochang: Got time to take a look?

ClusterFuzz has detected this issue as fixed in range 407167:409418.

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

Fuzzer: tokenfuzz_pdf_march16
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  CStretchEngine::CStretchEngine
  CFX_ImageStretcher::StartStretch
  CFX_ImageStretcher::Start
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_ubsan_chrome&range=370022:370027
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_ubsan_chrome&range=407167:409418

Minimized Testcase (1246.67 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95G1bVtaxFeRWR0KTfa5EUNpCnSHmKPLkfM-PVHANf-vLkHkdX3uaxse5Ub0xsoajItncBUIMl2uxcKI9Swq-_BQkGx-A4SmXJwOdu9PbFEed43O7H4wbbCh04PO-lQmRRE3boxvyZSJho55S5lzVQRp0Hi7NcVAa4xK41qpxu_YQL53qw?testcase_id=4897212719169536

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.

Not fixed. r633764 broke the PDF viewer's ability to load PDFs off disk.

Err, meant to say r408654 /  bug 633764 .

ClusterFuzz has detected this issue as fixed in range 407167:409418.

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

Fuzzer: tokenfuzz_pdf_march16
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  CStretchEngine::CStretchEngine
  CFX_ImageStretcher::StartStretch
  CFX_ImageStretcher::Start
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_ubsan_chrome&range=370022:370027
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_ubsan_chrome&range=407167:409418

Minimized Testcase (1246.67 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95G1bVtaxFeRWR0KTfa5EUNpCnSHmKPLkfM-PVHANf-vLkHkdX3uaxse5Ub0xsoajItncBUIMl2uxcKI9Swq-_BQkGx-A4SmXJwOdu9PbFEed43O7H4wbbCh04PO-lQmRRE3boxvyZSJho55S5lzVQRp0Hi7NcVAa4xK41qpxu_YQL53qw?testcase_id=4897212719169536

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.

ClusterFuzz testcase is verified as fixed, closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

ClusterFuzz has detected this issue as fixed in range 407167:409418.

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

Fuzzer: tokenfuzz_pdf_march16
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  CStretchEngine::CStretchEngine
  CFX_ImageStretcher::StartStretch
  CFX_ImageStretcher::Start
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_ubsan_chrome&range=370022:370027
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_ubsan_chrome&range=407167:409418

Minimized Testcase (1246.67 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95G1bVtaxFeRWR0KTfa5EUNpCnSHmKPLkfM-PVHANf-vLkHkdX3uaxse5Ub0xsoajItncBUIMl2uxcKI9Swq-_BQkGx-A4SmXJwOdu9PbFEed43O7H4wbbCh04PO-lQmRRE3boxvyZSJho55S5lzVQRp0Hi7NcVAa4xK41qpxu_YQL53qw?testcase_id=4897212719169536

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.

Looks like a dup to a bug weili@ is fixing.

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

We have made a bunch of changes on ClusterFuzz side, so resetting ClusterFuzz-Wrong label.