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.

all 7 comments

sorted by: hot top controversial new old
[–] 55 points 1 day ago* (4 children)

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.

  • source
  • hideshow 4 child comments
  • [–] 33 points 1 day ago (1 child)

    Google has reportedly declined the bug report

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

  • source
  • hideshow 1 child comment
  • [–] 13 points 20 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.

  • source
  • parent