Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Predator could not provide any possible suspects.

From the below CL observing some changes related to 'CBORReader' hence suspecting the same
https://chromium.googlesource.com/chromium/src/+log/950384ffd4e30b1912c088d020e01794e78e98fa..2c188088b597e010d8bb4a75fb394a66682ed34c?pretty=fuller&n=10000

Suspect CL: https://chromium.googlesource.com/chromium/src/+/8abc3038960de43eb28bfe10cd6c058709dc9aad

kouhei@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

ClusterFuzz has detected this issue as fixed in range 538376:538378.

Detailed report: https://clusterfuzz.com/testcase?key=5377429397569536

Fuzzer: libFuzzer_ctap_response_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Ill
Crash Address: 0x7f4b34f96c57
Crash State:
  long base::internal::CheckOnFailure::HandleFailure<long>
  long base::internal::checked_cast<long, base::internal::CheckOnFailure, unsigned
  cbor::CBORReader::ReadMapContent
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=537717:537724
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=538376:538378

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5377429397569536

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.

ClusterFuzz testcase 5377429397569536 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.