Issue metadata
Sign in to add a comment
|
Direct-leak in OJPEGReadHeaderInfoSecTablesAcTable |
||||||||||||||||||||||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=4835653714182144 Fuzzer: libfuzzer_radamsa_pdf_codec_tiff_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Direct-leak Crash Address: Crash State: OJPEGReadHeaderInfoSecTablesAcTable OJPEGReadHeaderInfoSec OJPEGReadHeaderInfo Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=422880:422991 Minimized Testcase (0.50 Kb): https://cluster-fuzz.appspot.com/download/AMIfv955kgAbjhlWgtxK_qwJqLmn5_RlA_J1S8XUOTgxbxdTiEpt4esowvHjiDaKCz6LRGpypoq1XLUgFHwFqbCKXhcfkbMTIPVbY98S80luqlXV9fI-6G8hYvSbSd-_cDHr_HQZc8unokGFpyHQWSREjoaU0UEAXQ?testcase_id=4835653714182144 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Nov 1 2016
,
Nov 1 2016
This one should be easy. We need to free |rb| in the if(p!=q) block.
,
Nov 22 2016
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
,
Jan 12 2017
ClusterFuzz has detected this issue as fixed in range 442985:443138. Detailed report: https://cluster-fuzz.appspot.com/testcase?key=4835653714182144 Fuzzer: libfuzzer_radamsa_pdf_codec_tiff_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Direct-leak Crash Address: Crash State: OJPEGReadHeaderInfoSecTablesAcTable OJPEGReadHeaderInfoSec OJPEGReadHeaderInfo Sanitizer: address (ASAN) Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=422880:422991 Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=442985:443138 Minimized Testcase (0.50 Kb): https://cluster-fuzz.appspot.com/download/AMIfv955kgAbjhlWgtxK_qwJqLmn5_RlA_J1S8XUOTgxbxdTiEpt4esowvHjiDaKCz6LRGpypoq1XLUgFHwFqbCKXhcfkbMTIPVbY98S80luqlXV9fI-6G8hYvSbSd-_cDHr_HQZc8unokGFpyHQWSREjoaU0UEAXQ?testcase_id=4835653714182144 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 4835653714182144 is verified as fixed, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Jan 12 2017
Although clusterfuzz sample has been fixed (dup of 670928), still need to see if the suggestion of thestig@ in #3 should be implemented.
,
Jan 12 2017
Never mind, now we got bug 680520 , which is exactly this. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by msrchandra@chromium.org
, Nov 1 2016Components: Internals>Plugins>PDF
Labels: findit-wrong