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

Issue 698497 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Security



Sign in to add a comment

Use-of-uninitialized-value in v8::internal::compiler::NodeCache<int, v8::base::hash<int>, std::__1::equal_to<i

Project Member Reported by ClusterFuzz, Mar 4 2017

Issue description

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

Fuzzer: libfuzzer_v8_wasm_compile_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  v8::internal::compiler::NodeCache<int, v8::base::hash<int>, std::__1::equal_to<i
  v8::internal::compiler::JSGraph::Float32Constant
  v8::internal::wasm::WasmFullDecoder::DecodeFunctionBody
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

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

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv97xmy1GJkwUstwv-9Px8gf_R-SH8SbVlZs4Tr0Vm7gQGjV_P2Rc5LVL_X_No4u8-t7sUJHo5a4mTmBoke9j0fqg0qJspBsPLMkG3B81OhAhsCRlDWgP3lTuSHYgYHJw1s7s-1C74c9MPrcOvfTejEe6Luwi7WXWLTRL_8if2IgCP4xsToDvjyxZw24u4gNFhpurY7b05tHqwqW8w88IpEGg7So_jN_L_STvhXi1T0u9e2SiJsB1-i9Hj_oOi6Y5cSbpa15FIMO1KpOk3xmAILGtwquRgBNP-hrm4SR37TCKxh5I3uhgglLUCMjzC7zHNABmT9b2wHGsM51QQ6hzJB9cRgAos25VFE7uXnin_uhbol_5ZTw?testcase_id=5921169208508416


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, Mar 4 2017

Labels: M-58
Project Member

Comment 2 by sheriffbot@chromium.org, Mar 4 2017

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, Mar 4 2017

Labels: Pri-1

Comment 4 by vakh@chromium.org, Mar 5 2017

Cc: titzer@chromium.org
Components: Blink>JavaScript
Owner: mtrofin@chromium.org
Status: Available (was: Untriaged)
The regression range has no V8 CLs so I am not sure which CL caused it.
mtrofin@ -- please help triage this. Thanks.
Project Member

Comment 5 by sheriffbot@chromium.org, Mar 5 2017

Status: Assigned (was: Available)
Project Member

Comment 6 by ClusterFuzz, Mar 6 2017

ClusterFuzz has detected this issue as fixed in range 454791:454794.

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

Fuzzer: libfuzzer_v8_wasm_compile_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  v8::internal::compiler::NodeCache<int, v8::base::hash<int>, std::__1::equal_to<i
  v8::internal::compiler::JSGraph::Float32Constant
  v8::internal::wasm::WasmFullDecoder::DecodeFunctionBody
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=453545:453564
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=454791:454794

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv97xmy1GJkwUstwv-9Px8gf_R-SH8SbVlZs4Tr0Vm7gQGjV_P2Rc5LVL_X_No4u8-t7sUJHo5a4mTmBoke9j0fqg0qJspBsPLMkG3B81OhAhsCRlDWgP3lTuSHYgYHJw1s7s-1C74c9MPrcOvfTejEe6Luwi7WXWLTRL_8if2IgCP4xsToDvjyxZw24u4gNFhpurY7b05tHqwqW8w88IpEGg7So_jN_L_STvhXi1T0u9e2SiJsB1-i9Hj_oOi6Y5cSbpa15FIMO1KpOk3xmAILGtwquRgBNP-hrm4SR37TCKxh5I3uhgglLUCMjzC7zHNABmT9b2wHGsM51QQ6hzJB9cRgAos25VFE7uXnin_uhbol_5ZTw?testcase_id=5921169208508416


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 7 by ClusterFuzz, Mar 6 2017

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

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

Comment 8 by sheriffbot@chromium.org, Mar 6 2017

Labels: -Restrict-View-SecurityTeam Restrict-View-SecurityNotify
Labels: -ReleaseBlock-Beta -M-58 M-59
Project Member

Comment 10 by sheriffbot@chromium.org, Jun 12 2017

Labels: -Restrict-View-SecurityNotify allpublic
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

Sign in to add a comment