New issue
Advanced search Search tips

Issue 777272 link

Starred by 3 users

Issue metadata

Status: Duplicate
Owner: ----
Closed: Oct 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: Bug-Security



Sign in to add a comment

Security: Remote Password Extraction via autofill and compromised router

Reported by christop...@gmail.com, Oct 23 2017

Issue description

VULNERABILITY DETAILS
Chrome automatically enters saved passwords for HTTP pages.

When combined with basic attack tools another attackers on the same LAN and attackers in control of an upstream router can extract saved passwords from a users saved password list.

VERSION
Chrome Version: 62.0.3202.62 for Windows 10 - 64 Creator update and 
This problem also 61 on Android Nougat.

REPRODUCTION CASE (Basic)
*When the user browses to a http site that the user has saved a password for the password will be filled for insecure transmission.

REPRODUCTION CASE advanced
*Using a man in the middle attack (including arp cache poisioning).  Redirect the user to a login page for an http site that they have saved their password for.  When the user browser loads the login page add javascript to the network transmission that posts their username/password to your server.

Through a series of redirects the attacker could extract many passwords from a single user.

SOLUTION: COPY FIREFOX
*Firefox doesn't load the password for non-secured sites until the user clicks in the username filed and clicks pas the warning that says "this connection is not secure.  Logins entered here could be compromised".
 
Components: UI>Browser>Passwords
Status: Untriaged (was: Unconfirmed)
Summary: Security: Remote Password Extraction via autofill and compromised router (was: Security: Remote Password Extraction)
Chrome does not expose the password to JavaScript until a user gesture is received (see the PasswordValueGatekeeper class), although such protections are imperfect (see  Issue 681791  for discussion).

There's an active proposal to switch to Fill-on-Account-Select for non-secure contexts.

Comment 2 by tsepez@chromium.org, Oct 23 2017

Mergedinto: 568713
Status: Duplicate (was: Untriaged)
568713 is the (internal only, sorry) tracking bug for the proposal to mitigate this.
Project Member

Comment 3 by sheriffbot@chromium.org, Jan 30 2018

Labels: -Restrict-View-SecurityTeam allpublic
This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Will issue #568713 become public?  I would like to review that similar bug.
 Issue 818156  has been merged into this issue.

Comment 6 Deleted

Comment 7 Deleted

Sign in to add a comment