There's a vulnerability in uBlock Origin
There's no CVE because... GitHub didn't think of it?
There's a vulnerability in uBlock Origin
There's no CVE because... GitHub didn't think of it?
@wdormann please not my beloved ublock nooooo
@dey
I'm pretty sure that I had disabled updates, as I figured that the risk of supply chain compromise was greater than anything else. I guess I'll manually update it. 😂
@polishdub @dey
Here are more details:
https://iter.ca/post/ubo-uxss/
@wdormann GitHub is slow as fuck to assign CVEs. I requested one for this almost a month ago. https://github.com/OpenVoxProject/openvox/security/advisories/GHSA-ffr6-rwpm-p5wq
@binford2k
Assigning a number to a thing sounds very complicated.
@wdormann oh but I thought Manifest V2 was perfect and not a security risk and everyone who said it was paid by Google to kill ad blocks...or something. (Seriously, that narrative is way too popular)
@halezinflames @wdormann you're thinking of V3, which actually is a security improvement (hence why Firefox also adopted it), but Google cynically adopted in an unnecessarily adblock-hampering way
@halezinflames @volt4ire
Lite is significantly less capable than the regular version.
@wdormann @volt4ire The capability is still far more than "useless brick that doesn't block anything" that's heavily implied by the privacy-marketers. "MV3 killed ad block" implies no ads are blocked. Which is not true. Side by side I haven't noticed a difference big enough to care that much, all of the examples I hear about are theoreticals and stuff you don't see. I accept the change because for me it's not a big enough change for me to deal with the technical issues Firefox has on my machines