New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 662832 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

Use-of-uninitialized-value in utext_next32_58

Project Member Reported by ClusterFuzz, Nov 7 2016

Issue description

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6356259289956352

Fuzzer: libfuzzer_icu_ucasemap_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  utext_next32_58
  icu_58::RuleBasedBreakIterator::handleNext
  icu_58::RuleBasedBreakIterator::next
  
Recommended Security Severity: Medium

Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=429309:429390

Minimized Testcase (0.62 Kb): https://cluster-fuzz.appspot.com/download/AMIfv951c3NDvcXIMDdLJ14FX5ImXIE3P7f95NxfameIN6rR16gmTr4_d34ou_cgqaS7LzIFoMvA_YBz6cw23ENDpdPZUyfyO8QVeOcQ-tfHu4U1VmNAdTTTbtHUUhtiy52mViNZKmU9MQDMRQsX6kuvzlz7W8ERGw?testcase_id=6356259289956352

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
 
Project Member

Comment 1 by sheriffbot@chromium.org, Nov 7 2016

Labels: M-56
Project Member

Comment 2 by sheriffbot@chromium.org, Nov 7 2016

Labels: ReleaseBlock-Beta
This issue is a security regression. If you are not able to fix this quickly, please revert the change that introduced it.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 3 by sheriffbot@chromium.org, Nov 7 2016

Labels: Pri-1
Cc: mark@chromium.org jsb...@chromium.org
Components: UI>Internationalization
Owner: js...@chromium.org
Status: Assigned (was: Untriaged)
The ICU update to 58 is the likely cause of this regression: https://codereview.chromium.org/2442923002

jshin -- Can you take a look?

Comment 5 by js...@chromium.org, Nov 11 2016

Or, it can be just an old symptom rediscovered due to an icu symbol change (icu56_foo => icu58_foo). 

Anyway,sorry for the late reply. I'm looking at it. 

Comment 6 by js...@chromium.org, Nov 11 2016

Cc: aheninger@google.com
Oh... It's BreakIterator. Then, it is likely to be new. Adding aheninger@. 




Comment 7 by js...@chromium.org, Nov 11 2016

Labels: -Pri-1 -ReleaseBlock-Beta Pri-3
The API in question for title casing UTF-8 input is not used by Blink/Chrome/v8. 

Moreover, even if it's used, Chrome/v8/Blink would not feed invalid UTF-8 to the API that takes a UTF-8 string as an input, but the minimum test case uses an invalid UTF-8 string. 

Given these, I'm lowering the priority and removing Release-Block-Beta. 


Project Member

Comment 8 by sheriffbot@chromium.org, Nov 12 2016

Labels: ReleaseBlock-Beta
This issue is a security regression. If you are not able to fix this quickly, please revert the change that introduced it.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 9 by sheriffbot@chromium.org, Nov 26 2016

jshin: 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
Labels: -Type-Bug-Security -ReleaseBlock-Beta -Restrict-View-SecurityTeam -Security_Severity-Medium -Security_Impact-Head Type-Bug
Removing security flags based on #8.
Project Member

Comment 11 by ClusterFuzz, May 15 2017

ClusterFuzz has detected this issue as fixed in range 471616:471627.

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

Fuzzer: libfuzzer_icu_ucasemap_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  utext_next32_58
  icu_58::RuleBasedBreakIterator::handleNext
  icu_58::RuleBasedBreakIterator::next
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=429309:429390
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=471616:471627

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


See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Project Member

Comment 12 by ClusterFuzz, May 15 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 6356259289956352 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