New issue
Advanced search Search tips

Issue 735973 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Aug 8
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows
Pri: 3
Type: Bug

Blocking:
issue v8:5991
issue 757225



Sign in to add a comment

Crash in v8::internal::wasm::UnwrapImportWrapper with lazy compilation

Project Member Reported by ClusterFuzz, Jun 22 2017

Issue description

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

Fuzzer: inferno_js_fuzzer
Job Type: windows_asan_d8
Platform Id: windows

Crash Type: UNKNOWN READ
Crash Address: 0x2fd8a4b4
Crash State:
  v8::internal::wasm::UnwrapImportWrapper
  v8::internal::wasm::InstanceBuilder::ProcessImports
  v8::internal::wasm::InstanceBuilder::Build
  
Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=477767:477864

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


Issue filed automatically.

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
 
Cc: ahaas@chromium.org
Owner: clemensh@chromium.org
Status: Assigned (was: Untriaged)
More bugs for you :)
Project Member

Comment 2 by ClusterFuzz, Jun 22 2017

ClusterFuzz is analyzing your testcase. Developers can follow the progress at https://clusterfuzz.com/testcase?key=5587107656761344.
Cc: infe...@chromium.org machenb...@chromium.org
Any idea why all these wasm bugs dont reproduce on LINUX job types.
Sorry missed flags, let me add those first.
Project Member

Comment 5 by ClusterFuzz, Jun 22 2017

ClusterFuzz is analyzing your testcase. Developers can follow the progress at https://clusterfuzz.com/testcase?key=6621460897726464.
Project Member

Comment 6 by ClusterFuzz, Jun 22 2017

ClusterFuzz is analyzing your testcase. Developers can follow the progress at https://clusterfuzz.com/testcase?key=5830117736841216.
Project Member

Comment 7 by ClusterFuzz, Jun 22 2017

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

Job Type: linux_asan_d8_dbg
Crash Type: CHECK failure
Crash Address: 
Crash State:
  !it.done() in wasm-module.cc
  v8::internal::wasm::UnwrapImportWrapper
  UnwrapOrCompileImportWrapper
  
Sanitizer: address (ASAN)

Regressed: V8: 44043:44044

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


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
Components: -Blink>JavaScript Blink>JavaScript>WebAssembly
Labels: -Type-Bug-Security -Restrict-View-SecurityTeam -Security_Severity-Medium -Security_Impact-Head Pri-3 Type-Bug
Summary: Crash in v8::internal::wasm::UnwrapImportWrapper with lazy compilation (was: Crash in v8::internal::wasm::UnwrapImportWrapper)
Lowering priority, as this requires the --wasm-lazy-compilation command line flag.
It's also not security relevant.

The problem is that one instance imports an exported wasm function, and then tries to unwrap the js-to-wasm wrapper, but because this is using lazy compilation, there is no embedded WASM_FUNCTION code object. Hence a DCHECK fails / it crashes (depending on build mode).
Project Member

Comment 9 by ClusterFuzz, Jun 23 2017

Labels: OS-Linux
Blocking: v8:5991
Project Member

Comment 11 by ClusterFuzz, Jun 30 2017

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

Fuzzer: inferno_js_fuzzer
Job Type: linux_asan_d8_v8_arm64_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !it.done() in wasm-module.cc
  
Sanitizer: address (ASAN)

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


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
Project Member

Comment 12 by ClusterFuzz, Jul 5 2017

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

Fuzzer: inferno_js_fuzzer
Job Type: linux_asan_d8_v8_arm64_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !it.done() in wasm-module.cc
  
Sanitizer: address (ASAN)

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


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
 Issue 744320  has been merged into this issue.
Blocking: 757225
Project Member

Comment 15 by ClusterFuzz, Sep 16 2017

ClusterFuzz has detected this issue as fixed in range 48037:48038.

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

Job Type: linux_asan_d8_dbg
Crash Type: CHECK failure
Crash Address: 
Crash State:
  !it.done() in wasm-module.cc
  v8::internal::wasm::UnwrapImportWrapper
  UnwrapOrCompileImportWrapper
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=44043:44044
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=48037:48038

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

See https://github.com/google/clusterfuzz-tools 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 16 by ClusterFuzz, Sep 16 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 6398594272985088 is verified as fixed, so closing issue as verified.

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

Comment 17 by ClusterFuzz, Sep 24 2017

Labels: Needs-Feedback
ClusterFuzz testcase 4863300197416960 is still reproducing on tip-of-tree build (trunk).

Please re-test your fix against this testcase and if the fix was incorrect or incomplete, please re-open the bug. Otherwise, ignore this notification and add ClusterFuzz-Wrong label.
Cc: -machenb...@chromium.org -infe...@chromium.org
Status: Assigned (was: Verified)
Project Member

Comment 19 by ClusterFuzz, Oct 1 2017

Labels: Test-Predator-AutoComponents
Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 20 by ClusterFuzz, Oct 17 2017

ClusterFuzz has detected this issue as fixed in range 509045:509081.

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

Fuzzer: inferno_js_fuzzer
Job Type: windows_asan_d8
Platform Id: windows

Crash Type: UNKNOWN READ
Crash Address: 0x388e1496
Crash State:
  v8::internal::wasm::UnwrapImportWrapper
  v8::internal::wasm::InstanceBuilder::ProcessImports
  v8::internal::wasm::InstanceBuilder::Build
  
Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=477767:477864
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=509045:509081

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

See https://github.com/google/clusterfuzz-tools for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Labels: -Test-Predator-AutoComponents Test-Predator-Auto-Components
Status: Fixed (was: Assigned)
This is fixed, either by the jump table or already before that.

Sign in to add a comment