Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
[ID: 1223031]
Supplemental component tags only. Set main component first. [ID: 1222907]
[ID: 1223136]
Design doc to be reviewed. [ID: 1223032]
[ID: 1223087]
[ID: 1223134]
Milestone(s) impacted by this issue. [ID: 1223085]
[ID: 1223084]
[ID: 1223086]
[ID: 1223034]
Link to incidents in IRM as a result of this ticket. [ID: 1300460]
[ID: 1223088]
This field contains Gerrit urls of code changes that ‘fix’ a security bug (i.e., excluding logging/cleanup commits) and is used when a singular fix cannot be uniquely identified from the existing “Code Changes” field. The change can be in the chromium repo or any other third_party repo. [ID: 1358989]
[ID: 1253656]
View issue level access limits(Press Alt + Right arrow for more information)
Attachment actions
Unintended behavior
View staffing
Estimated effort
Description
Report description
Denial of Service (DoS) on Chrome via Large String Input in Text Field
Bug location
Where do you want to report your vulnerability?
Chrome VRP – Report security issues affecting the Chrome browser. See program rules
Which URL (or repository) have you found the vulnerability in?
vulnerability in the 'url' search field
The problem
Please describe the technical details of the vulnerability
Summary there is a DoS vulnerability in the search field or url provided by Google. so the vulnerability is that there is no limit on the number of characters, which allows the DoS attack to make the chrome browser not responding, causing lagging in chrome, and sometimes making the chrome tab CRASH or blank. previously I provided a table listing the possibility of this DoS attack succeeding. here are my test results
Test Result 10,000 characters = No effect, 50,000 characters = Slight lag, more 100,000 characters = Chrome crashes.
Impact analysis – Please briefly explain who can exploit the vulnerability, and what they gain when doing so
This attack has a situation:
the browser is not responding: the cause is because the user uses many extensions when pasting the payload
[a](/a/a/a/a/a/a/a/a/a.....(50000 times))
.browser that causes lagging: this situation works when the user has several extensions or has no extensions, the cause of lagging is because of pasting the load
[a](/a/a/a/a/a/a/a/a/a/a.....(50000 times))
which takes up a lot of memory.lastly, chrome tab crashes or goes blank: the situation when entering a very long text string into the input field. This bug can be executed through web pages, which means it can be used for DoS attacks against Chrome users if they visit malicious sites containing this payload. (this attack depends on the attacker's script, may be more dangerous if followed up)
How to reproduce situations 1 and 2
How to reproduce situation 3
Supporting references:https://hackerone.com/reports/557154
Impact: Malicious websites can load this payload automatically, making user tabs freeze or crash without the need for manual interaction.
Chrome with many extensions is more vulnerable to this bug, exacerbating the impact of the crash.
The cause
What version of Chrome have you found the security issue in?
135.0.7049.42 (Official Build) (64-bit) (cohort: Stable)
Is the security issue related to a crash?
Yes, it is related to a crash.
Choose the type of vulnerability
Denial of Service (DoS)
How would you like to be publicly acknowledged for your report?
Arif Rahman Huzaifa | Neicyy