New issue
Advanced search Search tips

Issue 910929 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: IsStringUTF8(*string_value_) in values.cc

Project Member Reported by ClusterFuzz, Dec 2

Issue description

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

Fuzzer: libFuzzer_chromeos_biod_storage_fuzzer
Job Type: libfuzzer_asan_chromeos
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  IsStringUTF8(*string_value_) in values.cc
  base::Value::Value
  base::DictionaryValue::SetString
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_asan_chromeos&range=3166387:3180910

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

Issue filed automatically.

See https://chromium.googlesource.com/chromiumos/docs/+/master/fuzzing.md#Reproducing-crashes-from-ClusterFuzz for more information.
 
Project Member

Comment 1 by ClusterFuzz, Dec 2

Cc: za...@chromium.org mqg@chromium.org norvez@chromium.org
Labels: ClusterFuzz-Auto-CC
Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.
Cc: cmt...@chromium.org
This is an interesting case. biod doesn't actually call WriteRecord() that way, the API usage is different. It's typically ReadRecordsForSingleUser() that is called first, then WriteRecord(). So those fields should(!) have been sanitised by other parts of the API first.
Project Member

Comment 3 by ClusterFuzz, Dec 4

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 6623911544094720 appears to be flaky, updating reproducibility label.
Labels: -Unreproducible Reproducible
Please ignore the last comment about testcase being unreproducible. 
The testcase is still reproducible. 
This was caused by a bug in ClusterFuzz that has been fixed. 
Sorry for the inconvenience.

Sign in to add a comment