New issue
Advanced search Search tips

Issue 894136 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 12
EstimatedDays: ----
NextAction: 2018-10-12
OS: ----
Pri: ----
Type: Bug-Security



Sign in to add a comment

Security: Google Chrome BACK button and sometimes Forward button expose sensitive information

Reported by ztele2...@gmail.com, Oct 10

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 READ THIS FAQ before filing a bug: https://chromium.googlesource.com
/chromium/src/+/master/docs/security/faq.md

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

Reports may be eligible for reward payments under the Chrome VRP:
http://g.co/ChromeBugRewards

NOTE: Security bugs are normally made public once a fix has been widely
deployed.

-------------------------

VULNERABILITY DETAILS
Please provide a brief explanation of the security issue.

This is in relation to Fidelity Investments. I found a way to access accounts by using the BACK arrow [and sometimes the FORWARD arrow] button on Google Chrome.  It may be a bug for many other websites that by using SQL injection or some other process can gain access to accounts or other private information. I have a small video that I can share upon request.

VERSION
Chrome Version: [x.x.x.x] + [stable, beta, or dev]
Operating System: [Please indicate OS, version, and service pack level]

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, or any personal or confidential information.

Please attach files directly, not in zip or other archive formats, and if
you've created a demonstration site please also attach the files needed to
reproduce the demonstration locally.

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

Browser exposes the client information for a few seconds allowing enough time for an SQL injection or some other input.

CREDIT INFORMATION
Externally reported security bugs may appear in Chrome release notes. If
this bug is included, how would you like to be credited?
Reporter credit: [goes here] D. Hill

 
Labels: Needs-Feedback
NextAction: 2018-10-12
This sounds like an issue with Fidelity investment site.

We cannot make any progress on this without some kind of details such as reproduction steps. Please revert with these details otherwise this bug will be closed by 2018-10-12.
The NextAction date has arrived: 2018-10-12
Labels: -Restrict-View-SecurityTeam -Needs-Feedback allpublic
Status: WontFix (was: Unconfirmed)

Sign in to add a comment