Another bug about properties defined on exported wasm functions.

This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it.

If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA.

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

ClusterFuzz has detected this issue as fixed in range 488064:488097.

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

Fuzzer: inferno_js_fuzzer
Job Type: windows_asan_d8
Platform Id: windows

Crash Type: UNKNOWN READ
Crash Address: 0x08200406
Crash State:
  v8::internal::WasmInstanceObject::module
  v8::internal::wasm::GetWasmFunctionForImportWrapper
  v8::internal::wasm::InstanceBuilder::ProcessImports
  
Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=485247:485271
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=488064:488097

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


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.

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