Closed Bug 1581417 Opened 5 years ago Closed 5 years ago

Measures against extension-originated leaks detailed in DataSpii report

Categories

(WebExtensions :: Untriaged, enhancement)

69 Branch
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1578284

People

(Reporter: sahal8020, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0

Steps to reproduce:

Read DataSpii report here https://securitywithsam.com/2019/07/dataspii-leak-via-browser-extensions/

Actual results:

I was appalled and found no public response from Mozilla team.

Expected results:

Read an acceptable response and commitments from people behind my favorite browser. For example:

Thanks!

Hi sahal8020,

Thanks for reporting this as an enhancement.

I'll add a product and component so the corresponding team can take a look at this and advice. If you consider this is not the right component, feel free to change it.

Regards,

Component: Untriaged → Security
Product: Firefox → Core
Component: Security → Untriaged
Product: Core → WebExtensions
Version: 69 Branch → Firefox 69

Mozilla has blocked the extensions that were found to be in violation of our policies.

Extension security is important to Mozilla, and our ecosystem has undergone several shifts over the years in response to changing threats.

In response, our recent focus has been on limiting the damage malicious extensions can do, helping users discover recommendations [1] that we vet and monitor, helping users understand the risks that come with installing extensions, and making it easier for users to report potentially malicious extensions to us.

  1. https://support.mozilla.org/en-US/kb/recommended-extensions-program

    Additionally, we are taking a look at how we ask for and grant host permissions as part of our Manifest version 3 work, so I'm closing this as duplicate of bug 1578284.
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
Version: Firefox 69 → 69 Branch
You need to log in before you can comment on or make changes to this bug.