Issue metadata
Sign in to add a comment
|
Heap-buffer-overflow in safe_browsing::dmg::ConvertBigEndian |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6655896104206336 Fuzzer: libFuzzer_safe_browsing_hfs_fuzzer Job Type: mac_libfuzzer_chrome_asan Platform Id: mac Crash Type: Heap-buffer-overflow READ 4 Crash Address: 0x602000002e70 Crash State: safe_browsing::dmg::ConvertBigEndian safe_browsing::dmg::ConvertBigEndian safe_browsing::dmg::HFSBTreeIterator::ReadCurrentLeaf Sanitizer: address (ASAN) Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=509376:509426 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6655896104206336 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Nov 30 2017
,
Dec 1 2017
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
,
Dec 1 2017
,
Dec 8 2017
,
Dec 15 2017
rsesek: Uh oh! This issue still open and hasn't been updated in the last 14 days. This is a serious vulnerability, and we want to ensure that there's progress. Could you please leave an update with the current status and any potential blockers? If you're not the right owner for this issue, could you please remove yourself as soon as possible or help us find the right one? If the issue is fixed or you can't reproduce it, please close the bug. If you've started working on a fix, please set the status to Started. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 30 2017
rsesek: Uh oh! This issue still open and hasn't been updated in the last 29 days. This is a serious vulnerability, and we want to ensure that there's progress. Could you please leave an update with the current status and any potential blockers? If you're not the right owner for this issue, could you please remove yourself as soon as possible or help us find the right one? If the issue is fixed or you can't reproduce it, please close the bug. If you've started working on a fix, please set the status to Started. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 4 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/d839eaa0fea5857b3a4226a0ee82ea5223b2b9bb commit d839eaa0fea5857b3a4226a0ee82ea5223b2b9bb Author: Robert Sesek <rsesek@chromium.org> Date: Thu Jan 04 02:36:34 2018 [Mac] Fix buffer-overread in safe_browsing::dmg::ConvertBigEndian. If the HFS volume header's reported variable-length node size is less than the size of a node's base header struct, the data are malformed. Bug: 790013 Change-Id: Ib61e48ad636170c935936fbb4795090c2f8c8f25 Reviewed-on: https://chromium-review.googlesource.com/849076 Reviewed-by: Nathan Parker <nparker@chromium.org> Commit-Queue: Robert Sesek <rsesek@chromium.org> Cr-Commit-Position: refs/heads/master@{#526902} [modify] https://crrev.com/d839eaa0fea5857b3a4226a0ee82ea5223b2b9bb/chrome/utility/safe_browsing/mac/hfs.cc
,
Jan 4 2018
,
Jan 5 2018
ClusterFuzz has detected this issue as fixed in range 526865:526949. Detailed report: https://clusterfuzz.com/testcase?key=6655896104206336 Fuzzer: libFuzzer_safe_browsing_hfs_fuzzer Job Type: mac_libfuzzer_chrome_asan Platform Id: mac Crash Type: Heap-buffer-overflow READ 4 Crash Address: 0x602000002e70 Crash State: safe_browsing::dmg::ConvertBigEndian safe_browsing::dmg::ConvertBigEndian safe_browsing::dmg::HFSBTreeIterator::ReadCurrentLeaf Sanitizer: address (ASAN) Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=509376:509426 Fixed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=526865:526949 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6655896104206336 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.
,
Jan 5 2018
ClusterFuzz testcase 6655896104206336 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Jan 5 2018
,
Feb 13 2018
,
Mar 27 2018
,
Apr 13 2018
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
, Nov 30 2017Owner: rsesek@chromium.org
Status: Assigned (was: Untriaged)