Issue metadata
Sign in to add a comment
|
Heap-use-after-free in blink::SVGResourcesCache::CachedResourcesForLayoutObject |
||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4536248216322048 Fuzzer: inferno_twister Job Type: windows_asan_chrome_no_sandbox Platform Id: windows Crash Type: Heap-use-after-free READ 8 Crash Address: 0x120b0cc346a0 Crash State: blink::SVGResourcesCache::CachedResourcesForLayoutObject blink::SVGResourcesCycleSolver::TraverseResourceContainer blink::SVGResourcesCycleSolver::TraverseResources Sanitizer: address (ASAN) Recommended Security Severity: High Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=556742:556743 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4536248216322048 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
May 8 2018
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/3431b89c8be2d7b1a60f5eb135b1d27ce432ce9b ([CI] Convert SVG resources to use SVGResource). 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.
,
May 8 2018
,
May 9 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
,
May 9 2018
,
May 10 2018
ClusterFuzz has detected this issue as fixed in range 557119:557122. Detailed report: https://clusterfuzz.com/testcase?key=4536248216322048 Fuzzer: inferno_twister Job Type: windows_asan_chrome_no_sandbox Platform Id: windows Crash Type: Heap-use-after-free READ 8 Crash Address: 0x120b0cc346a0 Crash State: blink::SVGResourcesCache::CachedResourcesForLayoutObject blink::SVGResourcesCycleSolver::TraverseResourceContainer blink::SVGResourcesCycleSolver::TraverseResources Sanitizer: address (ASAN) Recommended Security Severity: High Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=556742:556743 Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=557119:557122 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4536248216322048 See https://github.com/google/clusterfuzz-tools for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
May 10 2018
ClusterFuzz testcase 4536248216322048 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
May 10 2018
,
Jun 5 2018
,
Aug 16
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
, May 8 2018Labels: Test-Predator-Auto-Components