New issue
Advanced search Search tips

Issue 812730 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Security: extensions signing bypass

Reported by boha...@avast.com, Feb 15 2018

Issue description

VULNERABILITY DETAILS
It is possible to inject _arbitrary_ javascript into Chrome via an extension
that is signed by Google.

Right now malware is installing an old AdBlock extension (ver 409) into Chrome.

It drops these files:

Extensions\gighmmpiobklfepjocnamgkkbiglidom\449_0\_metadata\computed_hashes.json
Extensions\gighmmpiobklfepjocnamgkkbiglidom\449_0\_metadata\verified_contents.json
Extensions\gighmmpiobklfepjocnamgkkbiglidom\449_0\icon128.png
Extensions\gighmmpiobklfepjocnamgkkbiglidom\449_0\manifest.json
Extensions\gighmmpiobklfepjocnamgkkbiglidom\449_0\contentscript.js <- malicious script that gets loaded by Chrome

and modifies the 'Secure Preferences' file.


Then the extension gets loaded by Chrome without any security warnings.


I have attached all relevant files as well as a screenshot from Chrome.


The severity is probably low because by the time this happens the system is already infeceted with malware.


I would like to write a blogpost about it at blog.avast.com. So if you don't think that this is worth fixing, tell me as soon as possible.
On the other hand if you need some time to fix this, I will happily wait with publication of the blogpost.



VERSION
Chrome Version: 64.0.3282.167 (Official Build) (64-bit)
Operating System: Windows 10, 1709, build 16299.248

REPRODUCTION CASE
All the necessary files are attached in exp.7z. The password for the archive is 'infected'.

 
exp.7z
79.6 KB Download

Comment 1 by boha...@avast.com, Feb 15 2018

I am sorry for multiple submissions, I got "error 500" every time I tried to submit it.

Comment 2 by och...@chromium.org, Feb 15 2018

 Issue 812735  has been merged into this issue.

Comment 3 by och...@chromium.org, Feb 15 2018

 Issue 812736  has been merged into this issue.

Comment 4 by och...@chromium.org, Feb 15 2018

 Issue 812747  has been merged into this issue.

Comment 5 by och...@chromium.org, Feb 15 2018

 Issue 812748  has been merged into this issue.

Comment 6 by och...@chromium.org, Feb 15 2018

Status: WontFix (was: Unconfirmed)
Thanks for the report. As you mentioned we can't reasonably defend against malware installed on the machine we're running on. Please see https://chromium.googlesource.com/chromium/src/+/master/docs/security/faq.md#Why-arent-physically_local-attacks-in-Chromes-threat-model
Components: Platform>Extensions

Comment 8 by boha...@avast.com, Feb 15 2018

I thought that you would be interested to know that there is a way how to add an arbitrary extension to Chrome without turning the developer mode on and without Chrome complaining about it.
Project Member

Comment 9 by sheriffbot@chromium.org, May 25 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