- cross-posted to:
- privacy@programming.dev
- cross-posted to:
- privacy@programming.dev
A recently discovered bug in Android 16 allows any app to leak traffic outside the VPN tunnel.
The bug was reported to the Android Security Team, but was closed as Won’t Fix (Infeasible) […] In contrast, GrapheneOS, a security-focused Android-based OS, quickly patched the issue in its codebase.
A mitigation is possible, but is quite technical in that it requires USB debugging to be enabled on the device in order to run the following Android Debug Bridge (adb) commands:
adb shell device_config put tethering close_quic_connection -1
adb reboot
Yeah, haha sure, a bug… 🙄
ahh and it always seems somehow related back to QUIC!
nice, gonna use the fix as soon as I get home.
EDIT:
This disables the QUIC graceful shutdown feature, and thus closes the leak. The mitigation will persist across reboots, but it may be undone by system updates, in which case the steps will need to be repeated.
Performing this mitigation means that the server-side QUIC socket will remain half-open until it times out, which should generally not negatively affect the Android device or apps running on it. However, only use the command at your own risk if you understand the implications.
anyone knows the implications of this?
My guess is if the server side connection stays half open it would mean the server is still sending data to your device after its closed the connection causing that data to essentially get sinkhole’d.
Maybe in some extreme examples if you have a huge amount of connections that get abruptly closed your bandwidth could be limited until the connections expire. In normal circumstances that probably just means a small amount of additional background resources are getting wasted.
Android 16 introduced a bug
Security via poverty, like I can even run andriod 16 😎
Well, that’s what happens when you let foreign nationals to take over American corporations and run them only in the best interest of their nation, but not America or consumers.





