Abrt in sk_abort_no_print |
|||||||
Issue descriptionI think deserialization shouldn't assert and it should just fail gracefully. (1) allocInternal asserts if textSize < 0, so SkTextBlob::makeFromBuffer should check from this. (There's also inconsistency in terms of whether textSize is an int or a uint32_t. It kind of gets passed around as either, which is odd. Maybe they should all be one or the other?) (2) Same thing with glyph count. (3) The allocInternal font.getTextEncoding() assert also needs an early out.
,
Nov 20 2017
,
Nov 21 2017
ClusterFuzz is analyzing your testcase. Developers can follow the progress at https://clusterfuzz.com/testcase?key=4794789332779008.
,
Nov 21 2017
,
Nov 21 2017
,
Nov 21 2017
Detailed report: https://clusterfuzz.com/testcase?key=5092971900043264 Fuzzer: libFuzzer_paint_op_buffer_fuzzer Job Type: libfuzzer_chrome_asan_debug Crash Type: Abrt Crash Address: 0x03e900006848 Crash State: sk_abort_no_print SkTextBlobBuilder::allocInternal SkTextBlobBuilder::allocInternal Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=516777:516819 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5092971900043264 See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Nov 21 2017
ClusterFuzz has detected this issue as fixed in range 517957:518005. Detailed report: https://clusterfuzz.com/testcase?key=5092971900043264 Fuzzer: libFuzzer_paint_op_buffer_fuzzer Job Type: libfuzzer_chrome_asan_debug Crash Type: Abrt Crash Address: 0x03e900006848 Crash State: sk_abort_no_print SkTextBlobBuilder::allocInternal SkTextBlobBuilder::allocInternal Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=516777:516819 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=517957:518005 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5092971900043264 See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Nov 21 2017
ClusterFuzz has detected this issue as fixed in range 517979:518006. Detailed report: https://clusterfuzz.com/testcase?key=4794789332779008 Fuzzer: libFuzzer_paint_op_buffer_fuzzer Job Type: libfuzzer_chrome_asan Crash Type: Heap-buffer-overflow WRITE 4 Crash Address: 0x7f67d8577844 Crash State: SkTextBlob::RunRecord::RunRecord SkTextBlobBuilder::allocInternal SkTextBlobBuilder::allocRunText Sanitizer: address (ASAN) Recommended Security Severity: High Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=517979:518006 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4794789332779008 See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Nov 21 2017
ClusterFuzz testcase 4794789332779008 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Nov 21 2017
Detailed report: https://clusterfuzz.com/testcase?key=4794789332779008 Fuzzer: libFuzzer_paint_op_buffer_fuzzer Job Type: libfuzzer_chrome_asan Crash Type: Heap-buffer-overflow WRITE 4 Crash Address: 0x7f67d8577844 Crash State: SkTextBlob::RunRecord::RunRecord SkTextBlobBuilder::allocInternal SkTextBlobBuilder::allocRunText Sanitizer: address (ASAN) Recommended Security Severity: High Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=514197:514231 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=517979:518006 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4794789332779008 See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information. A recommended severity was added to this bug. Please change the severity if it is inaccurate. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by ClusterFuzz
, Nov 20 2017