New issue
Advanced search Search tips

Issue 680062 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Undefined-shift in CGifLZWDecoder::Decode

Project Member Reported by ClusterFuzz, Jan 11 2017

Issue description

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

Fuzzer: libfuzzer_pdf_codec_gif_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Undefined-shift
Crash Address: 
Crash State:
  CGifLZWDecoder::Decode
  gif_load_frame
  CCodec_GifModule::LoadFrame
  
Sanitizer: undefined (UBSAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_ubsan&range=400697:402043

Minimized Testcase (0.12 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94iuLaMHVrEOh4jv0aLZnTFgaZgnVfQcnsV8aRRVqpaBCYKFYOmICx0SU7NUsV6JO35IREG1P-eAMUh0bYR__PhDfOt8P4wf3Txcgm8QGmPFg06PvLwC5hsbUNBVOvmJzh-pfvZke98KRrHj3PGceBFKc6viA?testcase_id=4854821996986368

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
 
Cc: npm@chromium.org dsinclair@chromium.org
Components: Internals>Plugins>PDF
Labels: Test-Predator-Wrong M-55
Could not find exact culprit CL using findit, regression range and code search. cc-ed developer who worked on this. please take a look and reassign if needed.

Comment 2 by npm@chromium.org, Jan 16 2017

Cc: -npm@chromium.org
Owner: npm@chromium.org
Status: Assigned (was: Untriaged)
Project Member

Comment 3 by bugdroid1@chromium.org, Jan 16 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/386b2a829c8ca86b04fad4ae527a35991b872bd0

commit 386b2a829c8ca86b04fad4ae527a35991b872bd0
Author: pdfium-deps-roller <pdfium-deps-roller@chromium.org>
Date: Mon Jan 16 19:34:28 2017

Roll src/third_party/pdfium/ 38c866022..135609831 (1 commit).

https://pdfium.googlesource.com/pdfium.git/+log/38c8660228cc..135609831bca

$ git log 38c866022..135609831 --date=short --no-merges --format='%ad %ae %s'
2017-01-16 npm Return error when bits_left is too big

BUG= 680062 

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls

TBR=dsinclair@chromium.org

Review-Url: https://codereview.chromium.org/2635063002
Cr-Commit-Position: refs/heads/master@{#443934}

[modify] https://crrev.com/386b2a829c8ca86b04fad4ae527a35991b872bd0/DEPS

Project Member

Comment 4 by ClusterFuzz, Jan 17 2017

ClusterFuzz has detected this issue as fixed in range 443924:443941.

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

Fuzzer: libfuzzer_pdf_codec_gif_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Undefined-shift
Crash Address: 
Crash State:
  CGifLZWDecoder::Decode
  gif_load_frame
  CCodec_GifModule::LoadFrame
  
Sanitizer: undefined (UBSAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_ubsan&range=400697:402043
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_ubsan&range=443924:443941

Minimized Testcase (0.12 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94iuLaMHVrEOh4jv0aLZnTFgaZgnVfQcnsV8aRRVqpaBCYKFYOmICx0SU7NUsV6JO35IREG1P-eAMUh0bYR__PhDfOt8P4wf3Txcgm8QGmPFg06PvLwC5hsbUNBVOvmJzh-pfvZke98KRrHj3PGceBFKc6viA?testcase_id=4854821996986368

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Project Member

Comment 5 by ClusterFuzz, Jan 17 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 4854821996986368 is verified as fixed, so closing issue.

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

Sign in to add a comment