inferno/mbarbella could you please help triage this? It looks like the ipc fuzzer code calling into hunspell.

Ignore that, I just realized we're fuzzing hunspell. groby: could you please help triage? Thanks!

We shouldn't be fuzzing hunspell :)

At least not the way we're doing it right now - hunspell is being fuzzed using invalid UTF8, and that violates the basic contract for hunspell.

CL to address this is WIP at  https://codereview.chromium.org/2223603002/

groby: 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

ClusterFuzz has detected this issue as fixed in range 414856:414881.

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

Fuzzer: libfuzzer_hunspell_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  Hunspell::spell
  Hunspell::suggest
  _start
  
Recommended Security Severity: Medium

Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=414856:414881

Minimized Testcase (0.06 Kb):
Download: https://cluster-fuzz.appspot.com/download/AMIfv963jErz_UEv0mna-e3yHIes31hct67qLigH5pX99rLr881_A12Y07hMZ3RkO1KOohujr54EvnRhHlMU9YoLxcuz-IE1USH-I9i0ydywDYbh9Li2mS40t1tTSHBzgJjxXrbAQGKjgfqT855F3P7XlQ1XWuGwVw?testcase_id=5874795044667392
I-unfortunately--senstiveatibilitiesrns>4x-88---<?v;ry-)�


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.

ClusterFuzz testcase is verified as fixed, closing issue.

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

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