Issue metadata
Sign in to add a comment
|
Use-of-uninitialized-value in blink::ColorSpaceUtilities::GetColorSpaceGamut |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5726553691127808 Fuzzer: libFuzzer_blink_png_decoder_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Use-of-uninitialized-value Crash Address: Crash State: blink::ColorSpaceUtilities::GetColorSpaceGamut blink::BitmapImageMetrics::CountImageGammaAndGamut blink::ImageDecoder::DecodeFrameBufferAtIndex Sanitizer: memory (MSAN) Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=552556:552571 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5726553691127808 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Apr 21 2018
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/371ffcdbb5dca7fb1a0aeb53956905bb1d4f9fc5 ([SPv175] Repaint non-composited layer on layer visibility change). If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
,
Apr 21 2018
,
Apr 22 2018
,
Apr 22 2018
This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it. If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 22 2018
,
Apr 22 2018
,
Apr 22 2018
,
Apr 23 2018
,
Apr 23 2018
,
Apr 23 2018
Looking at the code that's failing, pretty sure https://skia-review.googlesource.com/c/skcms/+/122951 will fix this one, too.
,
Apr 23 2018
Fixed by https://skia.googlesource.com/skia/+/b7eace414d9239b146fc8ec1a259eeacbd9508df
,
Apr 24 2018
,
Apr 25 2018
ClusterFuzz has detected this issue as fixed in range 553087:553094. Detailed report: https://clusterfuzz.com/testcase?key=5726553691127808 Fuzzer: libFuzzer_blink_png_decoder_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Use-of-uninitialized-value Crash Address: Crash State: blink::ColorSpaceUtilities::GetColorSpaceGamut blink::BitmapImageMetrics::CountImageGammaAndGamut blink::ImageDecoder::DecodeFrameBufferAtIndex Sanitizer: memory (MSAN) Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=552556:552571 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=553087:553094 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5726553691127808 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.
,
Apr 25 2018
ClusterFuzz testcase 5726553691127808 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Apr 30 2018
,
Jul 31
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 ClusterFuzz
, Apr 21 2018Labels: Test-Predator-Auto-Components