Integer-overflow in SkDropShadowImageFilter::onFilterImage |
|||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=5031658865819648 Fuzzer: ifratric-browserfuzzer-v3 Job Type: linux_ubsan_chrome Platform Id: linux Crash Type: Integer-overflow Crash Address: Crash State: SkDropShadowImageFilter::onFilterImage SkImageFilter::filterImage SkImageFilter::filterInput Sanitizer: undefined (UBSAN) Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_ubsan_chrome&range=441240:441358 Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv94eGuzE15NExkPCJ_qWKFsVWeRiJjoxj2cpJLl-F5MeGW_RrolMUoR-uNtgoOTZuVctbDX5AiqhLsMYyS0nHKqJwLxK0_C2BvhsbaSoUjCNlJwfY1ZRZ7Ykjt6kihXawkq-HHiLaLna4gCt6zKWuK7dTitnTEvJIaVdJqwiiE1dGJAfh9YKDRK76l4TDjK_7VK4rQghvV-ctrzdedbQmG0I9AF1UD3PVyl4y3fAM4WzVXBLmJYTC5kKYNFf2OhqRuOcq8ooSAbv25e9QHaIQuECInMmAONIkqHL4TuXPkBAirqlvymxcSDaitEf-Qb5P2nsRJ0oBuQMgUuExnJV4N0nC1hw8LXcv5KbPOC9d_lJMaIW5-0?testcase_id=5031658865819648 Issue filed automatically. See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Mar 7 2017
In a quick look at the code, it appears an integer overflow here would result in us just not drawing the filter- not put us in a compromised state. I think this is a won't fix issue, but cc Robert/Mike to double check my assessment.
,
Mar 31 2017
ClusterFuzz has detected this issue as fixed in range 460819:460851. Detailed report: https://clusterfuzz.com/testcase?key=5031658865819648 Fuzzer: ifratric-browserfuzzer-v3 Job Type: linux_ubsan_chrome Platform Id: linux Crash Type: Integer-overflow Crash Address: Crash State: SkDropShadowImageFilter::onFilterImage SkImageFilter::filterImage SkImageFilter::filterInput Sanitizer: undefined (UBSAN) Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=441240:441358 Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=460819:460851 Reproducer Testcase: https://clusterfuzz.com/download/AMIfv94eGuzE15NExkPCJ_qWKFsVWeRiJjoxj2cpJLl-F5MeGW_RrolMUoR-uNtgoOTZuVctbDX5AiqhLsMYyS0nHKqJwLxK0_C2BvhsbaSoUjCNlJwfY1ZRZ7Ykjt6kihXawkq-HHiLaLna4gCt6zKWuK7dTitnTEvJIaVdJqwiiE1dGJAfh9YKDRK76l4TDjK_7VK4rQghvV-ctrzdedbQmG0I9AF1UD3PVyl4y3fAM4WzVXBLmJYTC5kKYNFf2OhqRuOcq8ooSAbv25e9QHaIQuECInMmAONIkqHL4TuXPkBAirqlvymxcSDaitEf-Qb5P2nsRJ0oBuQMgUuExnJV4N0nC1hw8LXcv5KbPOC9d_lJMaIW5-0?testcase_id=5031658865819648 See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Mar 31 2017
ClusterFuzz testcase 5031658865819648 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 |
|||
Comment 1 by msrchandra@chromium.org
, Mar 7 2017