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

Issue 750426 link

Starred by 1 user
Status: WontFix
Owner:
karandeepb@chromium.org
Closed: Aug 30
Cc:
karandeepb@chromium.org
pnangunoori@chromium.org
█ msrchandra@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Null-dereference READ in extensions::ExecuteCodeInTabFunction::Init

Project Member Reported by ClusterFuzz, Jul 29 2017 
Detailed report: https://clusterfuzz.com/testcase?key=4547331549822976

Fuzzer: ipc_fuzzer_mut
Job Type: linux_asan_chrome_ipc
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000188
Crash State:
  extensions::ExecuteCodeInTabFunction::Init
  extensions::ExecuteCodeInTabFunction::HasPermission
  extensions::ExtensionFunctionDispatcher::CheckPermissions
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_ipc&range=488146:488166

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


Issue filed automatically.

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

Comment 1 by msrchandra@chromium.org, Jul 31 2017

Cc: msrchandra@chromium.org
Labels: M-62 Test-Predator-Wrong
Owner: catmulli...@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL did not provide any possible suspects.
Using Code Search for the file, "tabs_api.cc" assigning to the concern owner.

Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/a41a43d5401c4080c7d71bac6d18ac9d85c25f26

@catmullings -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

Comment 2 by catmulli...@chromium.org, Aug 1 2017

Owner: ----
Status: Untriaged (was: Assigned)
Thanks for catching the crash. However, the crash is unrelated to my change. 

It looks like the null-dereference read is happening here (https://chromium.googlesource.com/chromium/src/+/f5345de13668f0176b11126a7ae391dad5b4ad0f/chrome/browser/extensions/api/tabs/tabs_api.cc#1836) on extension->id().

Comment 3 by karandeepb@chromium.org, Aug 8 2017

Cc: karandeepb@chromium.org

Comment 4 by pnangunoori@chromium.org, Sep 14 2017

Cc: pnangunoori@chromium.org
Labels: Test-Predator-Wrong-CLs
Owner: karandeepb@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.
Using the code search for the file, “extension_function_dispatcher.cc” assigning to concern owner from GIT revision log.

Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/627b05602fd345e010ebf553e56ccdacf211bf82

@karandeepb-- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.

Thank You.
Project Member

Comment 5 by ClusterFuzz, Oct 1 2017

Components: Platform>Extensions
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.

Comment 6 by mbarbe...@chromium.org, Nov 7 2017

Labels: -Test-Predator-AutoComponents Test-Predator-Auto-Components
Project Member

Comment 7 by ClusterFuzz, Aug 30

Status: WontFix (was: Assigned)
ClusterFuzz testcase 4547331549822976 is flaky and no longer crashes, so closing issue.

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

Sign in to add a comment