New issue
Advanced search Search tips

Issue 611875 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: May 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: Bug



Sign in to add a comment

Security: Chrome Internet Settings Proxy not applied after 50+ tabs open.

Reported by wwzhan...@gmail.com, May 13 2016

Issue description

This template is ONLY for reporting security bugs. If you are reporting a
Download Protection Bypass bug, please use the "Security - Download
Protection" template. For all other reports, please use a different
template.

Please see the following link for instructions on filing security bugs:
http://www.chromium.org/Home/chromium-security/reporting-security-bugs


VULNERABILITY DETAILS
I have proxy settings enabled on Internet Settings. After setting Chrome to use that same proxy settings, it works fine. However, after opening up 50+ tabs on Chrome, the proxy settings seems to be not working. 

VERSION
Chrome Version: [50.0.2661.75] + [stable]
Operating System: [Windows 7 OS, SP1]

REPRODUCTION CASE
Please include a demonstration of the security bug, such as an attached
HTML or binary file that reproduces the bug when loaded in Chrome. PLEASE
make the file as small as possible and remove any content not required to
demonstrate the bug.

FOR CRASHES, PLEASE INCLUDE THE FOLLOWING ADDITIONAL INFORMATION
Type of crash: [tab, browser, etc.]
Crash State: [see link above: stack trace, registers, exception record]
Client ID (if relevant): [see link above]

 
Components: Internals>Network>Proxy
Labels: -Type-Bug-Security -Restrict-View-SecurityTeam Type-Bug
I'm not able to reproduce this, but the preconditions make me skeptical that it would have much security impact. Reclassifying it as a bug and forwarding it along to some people who may be able to help.
Project Member

Comment 2 by sheriffbot@chromium.org, May 15 2017

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment