• kipo@lemm.ee
      link
      fedilink
      English
      arrow-up
      27
      ·
      3 months ago

      What do you mean? The article is talking about current versions of Android.

      • AmbiguousProps@lemmy.today
        link
        fedilink
        English
        arrow-up
        21
        arrow-down
        2
        ·
        edit-2
        3 months ago

        So the first line says that it’s for older versions of android before 2022. But the next paragraph says:

        For extremely specific use cases such as file managers, browsers or antivirus apps, Google grants an exception by allowing QUERY_ALL_PACKAGES permission, which provides full visibility into installed apps.

        So this may still be possible, however sandboxing, especially GrapheneOS’ implementation likely mostly, if not entirely reduce this risk.

        • kipo@lemm.ee
          link
          fedilink
          English
          arrow-up
          14
          ·
          3 months ago

          So this may still be possible

          This article seems to be saying that’s it’s not only possible, it’s being actively (and I would assume widely) exploited on current versions of Android. Google is supposed to catch any abuses of listed exceptions, but they are either missing a bunch or letting them intentionally slide through. Either way, apps being able to see other apps is a big security risk that IMO only the user should be able to explicitly allow, and on a case-by-case basis.

        • kipo@lemm.ee
          link
          fedilink
          English
          arrow-up
          9
          arrow-down
          1
          ·
          3 months ago

          Yeah, meaning all newer phones past Android 11 shouldn’t have this issue, but they do because of a workaround by shady companies that Google is either not aware of or not addressing. This issue isn’t limited to older phones – quite the opposite.

          • AmbiguousProps@lemmy.today
            link
            fedilink
            English
            arrow-up
            1
            arrow-down
            2
            ·
            3 months ago

            Apologies, I deleted my comment instead of editing it, but I meant to add that even with the shady workaround, if you have sandboxing it likely greatly reduces this risk.

            Be very wary of what apps you install, and in fact, try to only use FOSS.

    • DaGeek247@fedia.io
      link
      fedilink
      arrow-up
      10
      ·
      3 months ago

      The second half of the article talks about how the apps get around this permission requirement.

  • Nate@programming.dev
    link
    fedilink
    English
    arrow-up
    24
    ·
    3 months ago

    Seeing people say “GrapheneOS fixes this!” “It’s only on old versions of Android!”

    Device Info HW app that can read my applications

    Permissions requested (viewed in Google Play, lack of any "read applications" permission)

    Permissions granted in settings app, still lacking any "read applications" permission

    This is on a Pixel 8 Pro with the latest version of GrapheneOS. This is an issue and has been for a long time. Many apps detect root by looking for the Magisk package using this method, and many collect this information just for advertising (go ahead, export your Snapchat data)

  • kipo@lemm.ee
    link
    fedilink
    English
    arrow-up
    18
    ·
    3 months ago

    Well that was a horrifying read. Is there any software that can protect against this? GrapheneOS? LineageOS? A Magisk module?

    • Kairos@lemmy.today
      link
      fedilink
      English
      arrow-up
      3
      ·
      edit-2
      3 months ago

      Separate profiles, although graphene is supposedly working on it last I heard.

  • IllNess@infosec.pub
    link
    fedilink
    English
    arrow-up
    4
    ·
    3 months ago

    I know this happened a few years ago but would having a separate work profile through Shelter, Island, or Insular limit the app to only see those on the profile?