Hi Andreas,

Here's another wasm/testing/fuzzing security ticket.

Thanks!

The following revision refers to this bug:
  https://chromium.googlesource.com/v8/v8.git/+/e4ebd08c644da73562490aca189c9e482b8130cb

commit e4ebd08c644da73562490aca189c9e482b8130cb
Author: ahaas <ahaas@chromium.org>
Date: Thu Sep 15 09:26:52 2016

[wasm] Do proper bounds checking in the wasm interpreter for grow memory.

R=titzer@chromium.org

BUG= chromium:647027 

Review-Url: https://codereview.chromium.org/2344853002
Cr-Commit-Position: refs/heads/master@{#39440}

[modify] https://crrev.com/e4ebd08c644da73562490aca189c9e482b8130cb/src/wasm/wasm-interpreter.cc
[modify] https://crrev.com/e4ebd08c644da73562490aca189c9e482b8130cb/test/cctest/wasm/test-run-wasm-interpreter.cc

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

ClusterFuzz has detected this issue as fixed in range 418869:418964.

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

Fuzzer: afl_v8_wasm_code_fuzzer
Job Type: afl_chrome_asan
Platform Id: linux

Crash Type: Heap-use-after-free WRITE {*}
Crash Address: 0x7f6b795bb800
Crash State:
  v8::internal::wasm::ThreadImpl::Execute
  v8::internal::wasm::ThreadImpl::Run
  v8::internal::wasm::testing::InterpretWasmModule
  
Recommended Security Severity: High

Regressed: https://cluster-fuzz.appspot.com/revisions?job=afl_chrome_asan&range=418513:418554
Fixed: https://cluster-fuzz.appspot.com/revisions?job=afl_chrome_asan&range=418869:418964

Minimized Testcase (0.03 Kb):
Download: https://cluster-fuzz.appspot.com/download/AMIfv97PpYqW7jzFZq00Zu_lJJZ3AS2HwZT4cpUmtyyPNWl837t8vG6BducJCZz6maPg_oyTh7TxLBsV1Nld0lrwR2u8JXS7KOHw9BCdlSteSzM-cALuAulzcUZzVEjQOJqMj43kJd_uUF5iuOZRI1CMKTsjzmq0cg?testcase_id=6751705356304384
;;;;;;;;;;KY9W9NA99U99;99;;;


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