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

Issue 804075 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Jan 2018
Cc:
█ djmix....@samsung.com
dmazz...@chromium.org
aboxhall@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug
Team-Accessibility



Sign in to add a comment

Null-dereference READ in blink::AXMenuList::DidUpdateActiveOption

Project Member Reported by ClusterFuzz, Jan 20 2018 
Detailed report: https://clusterfuzz.com/testcase?key=4920924620193792

Fuzzer: mbarbella_webcomponents
Job Type: linux_ubsan_vptr_content_shell_drt
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  blink::AXMenuList::DidUpdateActiveOption
  blink::LayoutMenuList::UpdateFromElement
  blink::HTMLSelectElement::SelectOption
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=514498:517702

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Jan 20 2018

Components: Blink>Accessibility Blink>Layout
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 2 by ClusterFuzz, Jan 20 2018

Cc: djmix....@samsung.com dmazz...@chromium.org
Labels: Test-Predator-Auto-CC
Automatically adding ccs based on suspected regression changelists:

Fix naming of AXObject throughout Blink. by dmazzoni@chromium.org - https://chromium.googlesource.com/chromium/src/+/f1317f4bef330412662755fb32dd73634190ebec

Null dereference in AXMenuList::DidUpdateActiveOption by djmix.kim@samsung.com - https://chromium.googlesource.com/chromium/src/+/f2357fd60fcda8b432ad044e7d218b18abd4cb50

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

Comment 3 by e...@chromium.org, Jan 26 2018

Status: WontFix (was: Untriaged)
Not a security issue and not reported in the wild -> P3.
Realistically we do not have the resources to address this anytime soon.
Project Member

Comment 4 by ClusterFuzz, Feb 2 2018

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

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.

Comment 5 by brajkumar@chromium.org, Feb 16 2018 

 Issue 811025  has been merged into this issue.
►

Sign in to add a comment