TextInputController::SetMarkedText() should throw an exception for invalid parameters |
||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4561177744244736 Fuzzer: mbarbella_js_mutation_layout Job Type: linux_asan_content_shell_drt Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: start <= end (#text "NUMBER"@offsetInAnchor[1] vs. #text "NUMBER"@offsetInAnchor blink::TextIteratorAlgorithm<blink::EditingAlgorithm<blink::NodeTraversal> >::Te blink::DocumentMarkerController::AddMarkerInternal Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=475812:475824 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4561177744244736 Issue filed automatically. See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Jun 12 2017
,
Jun 13 2017
TextInputController#setMarkedText() takes uint32_t for start and end offsets,
we should make TextInputController#setMarkedText() to throw an exception for
invalid start/end offsets.
TextInputController::SetMarkedText(const std::string& text,
int start,
int length);
The issue is caused by following statement:
textInputController.setMarkedText('4294967295', -1, -1073741824);
where static_cast<uint32_t>(-1) > static_cast<uint32_t>(-1 + -1073741824);
,
Jun 14 2017
Lower to Pri-3, since this is caused by internal test method instead of real world application.
,
Oct 1 2017
Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.
,
Oct 4 2017
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/984f4b2c4df57ae840917a1d79f95a54e68e2c7b (Make TextIterator constructor to take only proper range). If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.
,
Oct 4 2017
Sorry for the reassignment. We just enabled this, but we should be ensuring that we don't assign to someone that's already removed themself as owner. Will fix on the ClusterFuzz side.
,
Nov 7 2017
,
Nov 7 2017
,
Nov 8
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 12
Unable to access the detailed report, hence adding CF-NeedsTriage label
,
Nov 13
|
||||||||||||
►
Sign in to add a comment |
||||||||||||
Comment 1 by msrchandra@chromium.org
, Jun 12 2017Labels: M-61 Test-Predator-Correct-CLs
Owner: yosin@chromium.org
Status: Assigned (was: Untriaged)