Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/3a79d5bcc58e2378f76c26c0120b66b23509c20f ([wasm] Move (almost all) constants to wasm-constants.h).
If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it.
If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA.
For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
ClusterFuzz testcase 4786452597309440 is verified as fixed, so closing issue as verified.
If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Automatically applying components based on crash stacktrace and information from OWNERS files.
If this is incorrect, please apply the Test-Predator-Wrong-Components label.
titzer@, does this bug have any security impacts? And if so, is the severity (High) accurate?
We need this information for the Chrome VRP panel, thanks!
I don't there was a security impact, because the check worked to prevent the unsafe situation properly (too large of memory). Earlier validation was needed.
Comment 1 by ClusterFuzz
, Aug 13Owner: titzer@chromium.org
Status: Assigned (was: Untriaged)