355

Any Chromium and Firefox browser prior to version 116 will be vulnerable to this, update your browsers.

top 50 comments
sorted by: hot top controversial new old
[-] Buelldozer@lemmy.today 100 points 1 year ago

This is way way wider than just browsers. Anything that can display webp images is vulnerable and that includes things like MS Teams and Twitch.

[-] Lantern@lemmy.world 50 points 1 year ago

Further solidifying webp as the worst image format.

[-] chameleon@kbin.social 20 points 1 year ago* (last edited 1 year ago)

The current advisory is in webm (VP8 specifically). The webp one was 2 weeks ago. ...yeah, not a good time for web browsers lately...

(edit: noticed OP actually did link the webp one, I thought it'd be CVE-2023-5217 because that's being linked elsewhere)

[-] Lucidlethargy@sh.itjust.works 14 points 1 year ago* (last edited 1 year ago)

WebP is currently the smallest and highest quality format accepted by browsers today. I have no idea why you think so negatively of it, but it's irreplaceable until something better is widely adopted, and thus viable.

It's the best format for websites as of this exact moment.

[-] mlg@lemmy.world 15 points 1 year ago

Highest compression, not highest quality (arguably).

Also heavy compression which takes more resources to display.

Also poor compatibility outside browsers.

afaik it's basically still just VP8 in image format with added metadata, and google refuses to support alternatives because they like to own the browser market.

I think there was gonna be a webp and webm 2, but it never happened.

[-] CriticalMiss@lemmy.world 7 points 1 year ago

The only reason that’s the case is because Google axed the JPEGXL implementation

[-] Espi@lemmy.world 4 points 1 year ago

AVIF is supported everywhere and it's fantastic

[-] jackpot@lemmy.ml 7 points 1 year ago
[-] CmdrShepard@lemmy.one 22 points 1 year ago

Try linking one and sending it to someone else. I tried it and the recipient died two days later.

load more comments (1 replies)
[-] gamer@lemm.ee 21 points 1 year ago

There's some politics involved. Basically, everyone is rallying behind JPEGXL instead of WebP, but Google refuses to support JPEGXL in Chrome. The reasoning they gave is weak, so it's assumed that they're just trying to force the format they invented on everyone because they can.

IIRC, performance of the two formats is similar.

[-] Dark_Arc@social.packetloss.gg 6 points 1 year ago
load more comments (5 replies)
[-] Lantern@lemmy.world 5 points 1 year ago

It’s a format that most major image editors don’t support. Basically, if you wanted to do anything with it, you need to first convert it to a different format. It’s the only format that has this problem.

[-] ipkpjersi@lemmy.ml 5 points 1 year ago

That's fair except it's not the only format that has this problem. There's JPEG 2000 and AVIF which have even less image editor support.

load more comments (1 replies)
load more comments (2 replies)
load more comments (1 replies)
load more comments (1 replies)
[-] shortwavesurfer@monero.town 60 points 1 year ago

Well, i think firefox 117 fixed that webp issue so i am on that one.

[-] joyjoy@lemm.ee 21 points 1 year ago

Specifically 117.0.1 (117.1 on android)

[-] ForestOrca@kbin.social 14 points 1 year ago* (last edited 1 year ago)

Good to go. Always roll with the latest version. 118.0.1

[-] c10l@lemmy.world 10 points 1 year ago
load more comments (5 replies)
[-] shortwavesurfer@monero.town 8 points 1 year ago

Yep. Fennec F-Droid 117.1.0

load more comments (3 replies)
[-] TylerDurdenJunior@lemmy.ml 51 points 1 year ago

idk. The post content was not in all caps, so I am not really sure about the urgency

[-] bappity@lemmy.world 32 points 1 year ago
[-] seaQueue@lemmy.world 17 points 1 year ago

It's last week's big libwebp vulnerability again.

load more comments (1 replies)
[-] GamingChairModel@lemmy.world 14 points 1 year ago

Sorta. OP just linked the full disclosure of the libwebp vulnerability that made the news 2 weeks ago.

But there's an even more recent vulnerability in libvpx that was announced this week, that is similar in a lot of ways (including severity).

[-] treadful@lemmy.zip 28 points 1 year ago

There's a more recent CVE as well for FF that was patched in 118.0.1: CVE-2023-5217: Heap buffer overflow in libvpx

[-] cheese_greater@lemmy.world 23 points 1 year ago

What actual like platforms does this affect and to what extent tho? Like Mac (probably not iOS which is WebKit)?

[-] towerful@programming.dev 20 points 1 year ago

I've read elsewhere it's actually a problem with libwebp not just chrome.
Basically, anything that relies on libwebp (ie can play libwebp) is vulnerable.
https://snyk.io/blog/critical-webp-0-day-cve-2023-4863/

load more comments (7 replies)
[-] Phen@lemmy.eco.br 14 points 1 year ago

Discord, slack, MS Teams, Steam, pretty much anything. But most of them have already fixed it so if you let stuff update itself frequently, there's little risk.

[-] Th3D3k0y@lemmy.world 13 points 1 year ago

Current Description

Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187 and libwebp 1.3.2 allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page. (Chromium security severity: Critical)

[-] cheese_greater@lemmy.world 4 points 1 year ago

By crafter webpage, does it mean it refers to anything like phishing or something a more savvy user wouldn't likely "fall for" or does that actually not matter (zero-day or whatever)

[-] Feathercrown@lemmy.world 9 points 1 year ago* (last edited 1 year ago)

Looks like it can do RCE without user interaction other than visiting the page-- not good!

load more comments (1 replies)
[-] pastermil@sh.itjust.works 21 points 1 year ago

I read this as RICE vulnerability and was confused

[-] PeWu@lemmy.ml 6 points 1 year ago

Yeah, Linux boys would be mad

[-] Turun@feddit.de 5 points 1 year ago* (last edited 1 year ago)

No, how could I be mad about the truth? We'd download and run any dotfiles if the screenshot looks nice enough.

load more comments (1 replies)
[-] eumesmo@lemmings.world 19 points 1 year ago

What about webview-based browsers in android phones?

[-] Bipta@kbin.social 13 points 1 year ago

As far as I'm aware this does affect Android and is not currently fixed. It's expected to be fixed in the October security patch.

This is just my memory of reading weeks ago. Someone else may know better.

[-] 9point6@lemmy.world 7 points 1 year ago

The Android webview is updated through the play store as of a few years ago

[-] Bipta@kbin.social 4 points 1 year ago

I believe the libwebp is implemented at the OS level. Again someone else may know better.

load more comments (1 replies)
[-] Vub@lemmy.world 10 points 1 year ago

Not sure why you only mention Chromium and Firefox in the post text, I can only assume this vulnerability affects ALL browsers. Safari (WebKit based) is, as far as I know, the second most used browser in the world.

load more comments (2 replies)
load more comments
view more: next ›
this post was submitted on 29 Sep 2023
355 points (95.2% liked)

Technology

58281 readers
6668 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS