69
Is Boost for Lemmy vulnerable to the webp exploit? (lemmy.world)
submitted 2 years ago by to c/boostforlemmy@lemmy.world
17 comments fedilink hide all child comments
 

What version of libwebp does Boost use and if it is currently vulnerable, when can we expect an update to fix this issue? The affected versions of libwebp are 0.5.0 to 1.3.1.

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 2 points 2 years ago (2 children)

Ah ok, I'll just stop using Boost until the October pixel update rolls out then

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 33 points 2 years ago (1 child)

    You should stop using your phone entirely if you're that worried.

    The vast majority of apps use the Android Web View component. No point in rolling their own, really.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] [S] 1 point 2 years ago

    Not really, just temporarily not using apps where random people can post images that are not re-encoded. Turns out this is very few apps, but sadly every lemmy app falls under this category.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 15 points 2 years ago (3 children)

    Surely Android provides security updates?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 11 points 2 years ago* (2 children)

    Depending on where the library lives in the Android ecosystem the update could be pushed by the play store framework as part of it's self-update capability or it could be pushed by the OEM with the next system OTA. If it's part of a system update you're at the mercy of the OEM's OTA schedule, Samsung hasn't pushed anything for my tablet in like 8mo, same for my OnePlus phone before the update this week.

    Based on this discussion here (https://news.ycombinator.com/item?id=37658635) it sounds like we're all waiting for an OEM OTA, for some reason the video codecs are rolled into the play framework's updates but not the image decoding libraries.

    People running LineageOS and other AOSP based firmwares should be covered after their ROMs integrate the next month security patch.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 2 years ago (1 child)

    So there is no central framework for pushing fixes to urgent fixes? Patching zero-days?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 2 years ago (2 children)

    Welcome to the wonderful world of Android. They're rolled into the monthly AOSP security patch and end users are at the mercy of the OEM's update schedule.

    This is why Pixel phone regular updates are a big deal, and a reason to run a regularly updated third party ROM like LineageOS.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 3 points 2 years ago

    This is why Pixel phone regular updates are a big deal, and a reason to run a regularly updated third party ROM like LineageOS.

    This is the very reason why I use LineageOS (as well as getting rid of bloatware).

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 2 years ago (1 child)

    As a person that’s been rolled into smartphones via work (iPhone 3Gs) and then never daily driven an Android, but always thought it might be more to my liking, I’m aghast. How can this be accepted? I now understand why large botnets often is comprised of Android devices.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago* (last edited 2 years ago)

    Zero days aren't the big driver of botnets, there are millions (if not hundreds of millions) of very cheap, very old, android devices out there. If you look at the periodic stats Google releases >50% of devices are running an Android version <= 10. Something like 20% of Android devices (at least according to the stats Google provides) running Android <= 5.

    Per earlier this year: https://m.gsmarena.com/android_13_is_now_running_on_12_of_devices_in_the_wild-news-58244.php

    I'm assuming these stats don't even cover a huge number of cheap Indian or Chinese devices too, those don't come with Google services at all.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 4 points 2 years ago (1 child)

    Yeah, they're monthly. So the next one is in October like OP said.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 2 years ago (1 child)

    That's dependent on carriers in a fair few cases or phone manufacturers in others. A lot of budget phones don't get timely security patches.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [+] 1 point 2 years ago (1 child)
    [deleted]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 years ago*

    I'm sure it can. The question is, will it. Part of the reason Google started updating apps on their side and removing feature updates from Android was because carriers and service providers weren't quick to update anything including security updates. It's one of the big selling points of the pixel line of phones. RCS is a very good example. The main cell providers did not want to take on RCS messaging and went as far as trying to make their own fork. They've done this with wallet apps back in the day as well.

    https://9to5google.com/2019/10/25/us-carriers-rcs-android-initiative/

    https://www.engadget.com/amp/2019-10-18-google-verizon-t-mobile-pixel-4-rcs-messaging.html

    https://www.idropnews.com/news/att-t-mobile-and-verizon-have-given-up-on-their-imessage-killer/156434/

  • permalink
  • fedilink
  • source
  • parent