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

Issue 675464 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Integer-overflow in blink::CounterNode::computeCountInParent

Project Member Reported by ClusterFuzz, Dec 18 2016

Issue description

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

Fuzzer: miaubiz_svg_fuzzer
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  blink::CounterNode::computeCountInParent
  blink::CounterNode::recount
  blink::makeCounterNodeIfNeeded
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_ubsan_chrome&range=389413:389420

Minimized Testcase (4.32 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94_CNibnFVjF9ckgp4pY223E2fEnm-LC7oLDGMWFNl9m2xEhdwmw016RB5LeB1FlCnyFb1rFvfpg1b_9ibqngCHRKyLH6F4YGBX2RjAg3LvWLOheYWCPGNzPq7bweRMNb2S6flj7mpnWiezCNMavCYZ9l-Qdg?testcase_id=6273942065250304

Issue filed automatically.

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

Comment 1 by tkent@chromium.org, Dec 18 2016

Components: Blink>Layout
Cc: msrchandra@chromium.org
Labels: Test-Predator-Wrong-CLs
Owner: e...@chromium.org
Status: Assigned (was: Untriaged)
Find it and CL did not provide any possible suspect.
Using Code Search for the file, "CounterNode.cpp" assigning to the concer owner.

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

Comment 3 by e...@chromium.org, Feb 21 2017

Status: WontFix (was: Assigned)
Non-security int overflows are considered WontFix.
Project Member

Comment 4 by ClusterFuzz, Jul 14 2017

Labels: Needs-Feedback
ClusterFuzz testcase 6273942065250304 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.

Sign in to add a comment