Issue metadata
Sign in to add a comment
|
Use-of-uninitialized-value in TIFFReadDirectoryCheckOrder |
||||||||||||||||||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=6198546644860928 Fuzzer: libfuzzer_pdf_codec_tiff_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Use-of-uninitialized-value Crash Address: Crash State: TIFFReadDirectoryCheckOrder TIFFReadDirectory TIFFClientOpen Recommended Security Severity: Medium Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=422909:423055 Minimized Testcase (0.05 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97wHXCm7CJ0-cBxJqbUCYFFyHJEUkGfVDcbG8zUvpO8QnHdYp_yiHr6E_IKJuQmGRT13lxbwjKiFlWDCDU-nBDihJxk1A8vWtdT3l1kJKP7rtn1eaJkUaJHDF4rDrsP3f5VJd2WbBB29yo11azfThAlPfEn9A?testcase_id=6198546644860928 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Oct 5 2016
This issue is a security regression. If you are not able to fix this quickly, please revert the change that introduced it. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 5 2016
,
Oct 5 2016
Issue is upstream; unclear if this path can be reached in pdfium, in which case this might be severity none. Keeping at high out of an abundance of caution.
,
Oct 5 2016
,
Oct 5 2016
This is XFA only code so not enabled on any Chrome branch.
,
Oct 11 2016
,
Oct 13 2016
,
Oct 26 2016
dsinclair: Uh oh! This issue still open and hasn't been updated in the last 14 days. This is a serious vulnerability, and we want to ensure that there's progress. Could you please leave an update with the current status and any potential blockers? If you're not the right owner for this issue, could you please remove yourself as soon as possible or help us find the right one? If the issue is fixed or you can't reproduce it, please close the bug. If you've started working on a fix, please set the status to Started. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 9 2016
dsinclair: Uh oh! This issue still open and hasn't been updated in the last 28 days. This is a serious vulnerability, and we want to ensure that there's progress. Could you please leave an update with the current status and any potential blockers? If you're not the right owner for this issue, could you please remove yourself as soon as possible or help us find the right one? If the issue is fixed or you can't reproduce it, please close the bug. If you've started working on a fix, please set the status to Started. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 1 2016
XFA is off by default, so Impact-None for now.
,
Dec 1 2016
,
Jan 12 2017
ClusterFuzz has detected this issue as fixed in range 443057:443122. Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6198546644860928 Fuzzer: libfuzzer_pdf_codec_tiff_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Use-of-uninitialized-value Crash Address: Crash State: TIFFReadDirectoryCheckOrder TIFFReadDirectory TIFFClientOpen Sanitizer: memory (MSAN) Recommended Security Severity: Medium Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=422909:423055 Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=443057:443122 Minimized Testcase (0.05 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97wHXCm7CJ0-cBxJqbUCYFFyHJEUkGfVDcbG8zUvpO8QnHdYp_yiHr6E_IKJuQmGRT13lxbwjKiFlWDCDU-nBDihJxk1A8vWtdT3l1kJKP7rtn1eaJkUaJHDF4rDrsP3f5VJd2WbBB29yo11azfThAlPfEn9A?testcase_id=6198546644860928 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.
,
Jan 12 2017
ClusterFuzz testcase 6198546644860928 is verified as fixed, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Jan 12 2017
,
Apr 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 sheriffbot@chromium.org
, Oct 5 2016