Bonum Certa Men Certa

Google Tricking Users Into Downloading WebP Images While WebP Format is Legally Hazardous and Also a Hazard for Computer Security

Reprinted with permission from Ryan Farmer.

Standards joke

(Credit: xkcd)



Google Tricking Users to Download WebP Images. WebP is Hazardous Legally and for Computer Security.



Some months back, Reddit handed me some WebP files, and I didn’t realize it at the time.



Months later, the problem has grown much worse and has apparently been spreading to other sites, due to caching servers.



This is worth mentioning since this week, Google’s WebP library had an emergency zero day vulnerability that enabled malicious code execution.



How serious was this emergency? Even Microsoft patched Edge on Windows 7.



This library is in Web browsers, photo manipulation tools, all sorts of things, and would not be contained even by the best sandbox, or even disabling active content in the Web browsers!



But wait, there’s more.



WebP is not widely used, and there are many articles like this one from LifeHacker which call WebP a pesky annoyance and show people how to convert them back to a legitimate image format.



WebP isn’t “better” enough in a compression efficacy sense to replace 1992 JPEG files. So almost everyone uses the 1992 JPEG standard to create image files.



They work everywhere, they’re fine. Why not?



Even though JPEG was finalized as a standard in 1992, and most of the patents went back to 1986, there were still patent lawsuits involving it in the courts, until 2013!



In just one example I found on Wikipedia, a patent troll claiming to have just one patent that JPEG infringed on extracted $104 million from nearly three dozen companies it shook down, before the patent was invalidated by victims who refused to pay and counter-sued, with the assistance of the JPEG Committee.



If the legal nightmare from software patents can go on for that long, and people who didn’t even invent the standard can sue you, why is WebM or AVIF (which is newer yet, and based off the AV1 video codec), “really safe” in the legal sense?



When you ask how Google or the “Alliance for Open Media” can guarantee that their redundant formats really are royalty-free, they just stop answering questions and disappear.



So now, thanks to Google and AOM, we have the proliferation of not just one, but two new formats that are not clearly “better” in the sense that anyone is using them willingly, and are dangerous in the legal and computer security sense of the word, and will be for decades.



Potentially, the patent lawsuits for AVIF will be finished in the 2040s, but by then, Google (if they’re still around) will have released at least five more pointless replacements for JPEG files.



Since Chrome will put it in and Google will deal with the lawsuits later, it will become a “standard” in the sense that everyone else with Web browsing software has to put it in to be compatible with Chrome and also risk being sued. Then everyone hosting the files on their Web site too.



Nothing has replaced JPEG for the same reason people still make new MP3 files.



Are they ideal? No.



But they were the first thing that were good enough to do the job, they’re legally safe, and the code has been around long enough to have been debugged and made predictable.



And they occupy a lot of mindshare.



Modern optimized JPEG encoders are quite good. It is, basically the image format of the Web and a lot of work has been put into giving people good encoders and working the bugs out of the decoders and making the decoders incredibly fast! On basically any hardware!



If I make a new JPEG using an optimized encoder on my laptop right now, you could open it on Windows 3.1. If you wanted to.



That’s an amazing amount of backward compatibility.



It’s in all software that handles images!



And, I don’t have to explain to mother what to do with one.



So what does Google do to force people to use it? They TRICK them!



When you use Chrome to download an image file, caching servers will send it a WebP because it’s faster and Chrome advertises compatibility with it.



Usually, these are transcoded from JPEGs that someone uploaded to the server, which is not a lossless process, into an even worse-looking WebM file that less software is compatible with.



I’ve caught Reddit doing this when I’m using a Chromium browser, but when I’m using SeaMonkey it sends me the JPEG. Firefox, it varies.



Probably the long term goal is that there will be so many of the damned things from people re-uploading the WebP that it will put pressure on anyone holding out on supporting the format.



Another possibility is that they don’t think you should be saving the images in the first place, so they’ll spit on you by handing you a degraded copy of the JPEG in some weird format.



It’s likely to happen with AVIF too. Google can’t make a standard because, apparently, they can’t even decide what covers their own use case.



The anti-trust case against Google should be looking at this.



Impressively, thanks to the fact that you could embed a WebP on Gemini as an object, if you could trick the user into displaying it, you could have Web-like vulnerability over Gemini thanks to Google’s stupid image format.



Codecs are very dangerous and having all of these codecs being added when they all basically do the same thing is making computing more hazardous.



Google has a long history of breaking the law and basically daring people to sue them.



It happened with their non-conformant Apache “Harmony” Java implementation, due to their rabid hatred of the GNU GPL (which is ironically now PROTECTING GOOGLE from further aggression from Oracle!)



They did it again with the original AAC encoder for Android. They paid a vendor to “steal” 3GPP source code and compile it, and FhG came knocking, which is why we have fdk-aac.



Google’s method of break the law and dare people to sue risks bringing modern computing down on top of us sometimes, like when Oracle sued and claimed APIs (in this case, Java), cold be copyrighted.



Well, say goodbye to almost anything you could write a computer program in if that argument flew. All so Google could use a bug-riddled and abandoned Apache “Java”.



And it’s happening all over again with video and image codecs.



There is, of course, another cost to having multiple codecs that do the same thing.



Bloat. Good old fashioned software bloat. Google has the resources to sit there and compile Chrome as many times as they want to. Compiling Chromium is beyond the capability of the average computer user at this point. There’s so much junk and garbage in there that the process takes forever and uses more memory than most computers even come with, ideally.



Just 10 years ago, you could compile most rendering engines on a laptop.



Today, Webkit is about the only one left where you can do it, or where it’s even all written in the same computer language.



Strangely, I recently wrote an article mocking IBM for claiming that compiling Webkit is hard.



They compile all the junk in Firefox and Chromium multiple times a day and nobody bats an eyelash.



Whether Google uses “open” media codecs or not doesn’t actually help you.



With Widevine and WEI, it’s clear that at some point even YouTube videos will be digitally encumbered. All of them. We face a future of the entire Web going “dark” and then it won’t really matter to the user what video “format” it’s in unless it’s “pirated”.



At some point, Web images might be like this too.



What did Mozilla get for selling us out? Is thirty pieces of silver still the going rate?



Netflix runs tests on codecs for the same reason Google does. It wants to keep its own bandwidth costs down, and nothing else. Since users don’t get a copy of anything they watch on Netflix, the format it is in on the server is wholly irrelevant.



Basically what these formats are promoted as, is a way for caching servers to spew files at you cheaply, and it hardly matters if the quality is good or not, or what the licensing of the codec is. How will a BSD license help you on the codec if it’s wrapped in DRM?



What does matter at the codec level, for you, is that when it comes through on your end, you now have dozens of times as many software vulnerabilities.



Not Google’s problem.

Recent Techrights' Posts

Richard Stallman About to Give More Talks in Europe, Some Confirmed Already
In Göteborg
Justice for Wildlife
animals cannot speak to humans who hate animals
GNU Was Right 42+ Years Ago
Since then the abusive, user-hostile technology has spread like mushrooms
Almost Half of the FSFE's Money (the Fake 'FSF', Misusing the Brand) Comes From Vodafone
That money always comes with strings, even if they're invisible to most of us
 
Linux is Not a Community Project, It's a Wall Street Product
The core goal should be freedom
Bad Actors Abusing the Free Software Community, Vandalising It Using Rogue Politics and Old Tactics
Oil giants have long attempted to do this; now, the digital equivalent of Big Oil does this in technology
Social Control Media Isn't the Future, The Federation or Fediverse Isn't Growing, People's Accounts Vanish for Good
users' accounts will get deleted, not just become inactive
IBM is Failing, This Helps Show Wall Street is Entirely Detached From Actual Commercial Performance
IBM is unable to grow, it's just constantly shrinking
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Tuesday, September 30, 2025
IRC logs for Tuesday, September 30, 2025
Clerical Aspects of Publishing and Development
In Free software, the management aspects are considerably reduced
Slopwatch: Fake Articles and Google News Promoting "Linux" Spam or Bot-Generated Fear, Uncertainty, Doubt (FUD)
These slopfarms help misplace blame
Third Wave of Microsoft Layoffs in September, This Time Many in Liverpool Affected
Be ready for more waves of layoffs ahead of the so-called "results" in late October
Gemini Links 30/09/2025: Motorcycling in Central Oregon, Protocol Styles and the Flag of Sark
Links for the day
Links 30/09/2025: Death Sentences, Internet Censorship, and Internet Shutdowns
Links for the day
Gemini Links 30/09/2025: Social Control Media and ROOPHLOCH
Links for the day
Links 30/09/2025: CERN in "Have I Been Pwned" and More Windows TCO Blunders
Links for the day
Microsoft Canonical is Selling Mass Surveillance and Back Doors as "Security for Ubuntu"
If you are looking for a GNU/Linux distro to use, just remember that Microsoft has Ubuntu in the bag
Cowboys Gonna Be Cowboys (on the Internet, They're Not a New Problem)
Boys will be boys
Cowboys of the "Left" and Cowboys of the "Right"
Don't believe the lie that this is some "leftist" thing
When Codes of Conduct Serve to Protect Criminals From Much-Deserved Scrutiny
CoCs are typically unfit for purpose because enforcement lacks context and suitable understanding of the full background (the "full story")
It Took the Open Source Initiative (OSI) 4+ Years to Address the 'Data Breach' or Data Protection Violation Reported to the California Privacy Protection Agency (CPPA) in March 2025
We may never know the dialogue or its nature
Even Microsoft's Biggest Boosters (and Media Operatives) Are Turning Against Microsoft
Expect many more layoffs before the fake "results" next month
Old Isn't Always Inadequate
How many gadgets manufactured today (in 2025) will still work in 2075?
The Monkey Business of Rust People
Compatibility won't matter
Microsoft Lunduke Spreads Deliberate Lies to Incite Online Mobs
Has he lost his reading comprehension skills?
Our 19th Birthday (in Just Over 5 Weeks From Now)
We meanwhile have ongoing, solid plans to cover patent-related issues when the FSF turns 40
British GNU/Linux Distro FydeOS Tops DistroWatch
That seems like a decent site and decent effort to keep an eye on
We'll Soon Have 75,000 GemText Pages
avoid many perils of today's Web
Google Used Free Software to Build a Monopoly. Now Google Kicks Free Software to the Curb
The "G" in "Google" does not stand for GNU. It never did. It's just another greedy company.
Gemini Links 30/09/2025: Retro Hardware, Federated Fragmentation, and Nex Server Written in C
Links for the day
4 More Days Till "4 decades, 4 freedoms, 4 all users"
We are now just 4 days away from the rare anniversary
Two Months After Merging to Hide GitHub Losses Microsoft is Doing It Again (This Time Windows)
Merging those two together is not a sign of strength but a tightening of budget
Speculations About the Next Large Wave of IBM/Red Hat Layoffs
the mass layoffs are likely to happen on week 3 or 4 in October
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Monday, September 29, 2025
IRC logs for Monday, September 29, 2025
Links 29/09/2025: Opposition to Surveillance Giant Google and Conflicts Worldwide (Moldova Sides With EU)
Links for the day
Why the EPO Never Managed to Silence Us (After Over a Decade of Trying)
Firms like Mishcon de Reya and Brett Wilson LLP contribute to a bad stigma, staining the entire occupation
Links 29/09/2025: Datacenter Fires and "Too Much Internet Use Is Changing Teenage Brains"
Links for the day
Almost a Couple of Years After Microsoft Hijacked the Name 'Sudo' (to Describe Unrelated Windows Stuff) Microsoft Canonical Breaks Sudo in Ubuntu
These are vandals in "goodwill" or "security" clothing
Does the Good Law Project (GLP) Know the Director of Brett Wilson LLP Deems It OK to Endorse Violent Actions Against Trans People?
We were miffed to see this morning's report
Names Are Not Unique IDs and the UK Government's "Digital ID System" Would be a Nightmare
Digital surveillance, "apps", and worse (all the time)
What is Roy and Rianne's Righteously Royalty-free RSS Reader?
A news reader that uses OPML files and parses RSS feeds
The Free Software Foundation (FSF) Turns 40 in 5 Days
We should be talking about software freedom, not "Open Source"
It Feels Like Brett Wilson LLP Has Just Tacitly Admitted That It Defamed Me
It arguably admitted many other things by refusing to deny or address them (altogether)
Stefano Maffulli's Front Page Mentions "AI" 11 Times
They're more focused on slop (plagiarism) than sharing or Software Freedom
CMS Rot
With "modern" (bloated) content management systems (CMSs) there is a long chain of dependencies
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Sunday, September 28, 2025
IRC logs for Sunday, September 28, 2025
Slopwatch: Fake Articles About Linux 6.17 and Microsoft Meddling in Linux Development
today's Slopwatch is short because the picks are from Sunday
Gemini Links 29/09/2025: The Labor Wars and Retro
Links for the day