The leak involves telling Android to create a keep-alive UDP connection that is offloaded to the hardware Wi-Fi or cellular chip.

GOS fix in progress. Google has reportedly declined the bug report/bounty.

  • pulsewidth@lemmy.world
    link
    fedilink
    English
    arrow-up
    59
    arrow-down
    1
    ·
    1 day ago

    Google sure seems to not care about VPN leak bugs that easily enable user apps to track real-world IP addresses without any kind of special permissions, even while the user thinks they’re safe in ‘lock traffic to VPN only mode’.

    I wonder why

    Via Graphene issue tracker.

    Author: ArminShupuk

    @thestinger As I see that you, Daniel, have picked this one up, I want to add that I was just in touch with Yusuf, who found the registerQuicConnectionClosePayload VPN leak. He informed me today that they didn’t pay him and closed the report as “won’t fix.” He had no success with his appeal. Mine seems to be “won’t fix” too, with no success reasoning with them either.

    So there are currently already two arbitrary ways for any user app with internet permission to leak the IP address in VPN lockdown mode that won’t be fixed upstream.

    Side note, the main GrapheneOS dev being his usual abrasive self (this is his only contribution to the thread).

    Author: thestinger

    That’s not the spelling of my name.

    • frongt@lemmy.zip
      link
      fedilink
      English
      arrow-up
      5
      ·
      12 hours ago

      I don’t see that comment in the linked issue. I do see them triaging and assigning it, though.

      • pulsewidth@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        41 minutes ago

        You do you (no downvote for me), but abrasiveness doesn’t help build community support in general, and context matters a lot.

        In the context of some random user demanding a niche feature be added to a free project to suit their needs: abrasiveness warranted.

        In the context here, of a security researcher very politely notifying them of a bug critical to the focus of their project (security and privacy), attempting private channels first, providijg deep details of the issue, adding discussion notes regarding upstream provider being unlikely to fix, and even including code to fix the problem for them - abrasiveness is counter-productive.

  • one_old_coder@piefed.social
    link
    fedilink
    English
    arrow-up
    36
    arrow-down
    2
    ·
    1 day ago

    Google has reportedly declined the bug report

    Yet another proof that preventing stores like F-droid is a good security choice /s

    • CosmicTurtle0 [he/him]@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      13
      ·
      24 hours ago

      In other words, Google prefers security researchers to immediately share vulnerability findings publicly immediately. That way users can properly mitigate their risks appropriately while Google decides whether fixing the vulnerability will affect their bottom line.