News for hackers. Stuff that matters.
Re:Chrome extensions are tampering with security headers by xg15 on Tuesday May 25, 2021 @09:45PM (#27285171)
I remember a not-so-long time ago that people were worried chrome would drop the extension system as a whole and therefore drop the ability of users to customise how they view web pages.

Now extensions are a "security threat". Here we go...

Re:Chrome extensions are tampering with security headers by kid-icarus on Tuesday May 25, 2021 @09:55PM (#27285247)
Yes, if an extension can override CSP directives to allow arbitrary connect-src exceptions, it effectively means that any data in any form on any page is now susceptible of having that data sent to an attacker-owned URL.

The solution doesn't necessitate removing extensions, it just means potentially constraining the API surface of extensions in order to mitigate the attack surface.

Re:Chrome extensions are tampering with security headers by postalrat on Wednesday May 26, 2021 @01:10AM (#27286622)
Extensions don't need to modify headers to view anything in the dom or make requests with the credentials of the page it's running in. The only thing it can't do is directly interact with the javascript running on the page (and vise versa).
Re:Chrome extensions are tampering with security headers by rini17 on Wednesday May 26, 2021 @07:45PM (#27297587)
This is misunderstanding. Extensions can read any data even with restrictive CSP. Malicious extension then can use other channel than the currently opened tab to exfiltrate them. There are many.

Extension users do want the extensions to interact with pages, often including cross-origin requests. That is what extensions are for and they won't work with restricting API surface.

Re:Chrome extensions are tampering with security headers by eli on Tuesday May 25, 2021 @09:51PM (#27285221)
both those things are true
Re:Chrome extensions are tampering with security headers by xg15 on Tuesday May 25, 2021 @09:55PM (#27285246)
Ok and now what?
Re:Chrome extensions are tampering with security headers by derefr on Tuesday May 25, 2021 @10:26PM (#27285453)
Is this snark meant to imply that you think that people shouldn't acknowledge a dilemma when one exists, unless they also have a solution to offer for said dilemma?

Google has nigh-on monopoly power over the browser ecosystem. Also, extensions are by-and-large malware. Making people aware that extensions are mostly malware helps Google to consolidate its monopoly; but also (obviously) helps people to avoid malware.

We don't want Google to control the Internet, and we don't want browsers to be full of malware. That's a dilemma. It has no obvious solution. But it's better to be aware of the dilemma — and so realize there is no easy solution — than to ignorantly push for one side or the other to "win."

Re:Chrome extensions are tampering with security headers by userbinator on Tuesday May 25, 2021 @10:58PM (#27285670)
At this point I'm convinced that there has to be a really strong opposition, or the Internet becomes Google's jail. We are basically seeing the dystopian side of "zero crime policies" acted out online as they slowly but surely evolve the definition of "malware" and erode away at our freedoms.

Google could be educating users to make their own responsible decisions, but it's far more profitable to keep them uninformed and feed them propaganda to maintain the paranoia that lets it monetise and take control away from them. Being ultimately an ad company, it thrives on deception.

and so realize there is no easy solution — than to ignorantly push for one side or the other to "win."

Twenty years ago, what Apple Google Microsoft do today with their software would be widely considered adware/spyware. One side has already won the battle; we can't let it win the war.

"Give me liberty or give me death," as the famous saying goes.