RetroFed Forums
Your home away from modern life.
Android NAT-T Keepalive Offload Bypasses VPN Lockdown: Device-Class Exposure Across Most Android 12+ Devices | Armin Šupuk
Post Reply
AuthorMessage
printf("%s", name);
piefed.blahaj.zone

akunohana@piefed.blahaj.zone
Joined: 2026-03-30
Posted:   Subject: Android NAT-T Keepalive Offload Bypasses VPN Lockdown: Device-Class Exposure Across Most Android 12+ Devices | Armin Šupuk Quote

Technical report on Android VPN lockdown bypass via NAT-T keepalive offload.

The direct attacker value is repeated real-network identity disclosure. A destination controlled by the attacker can learn the source IP address as seen from the physical Wi-Fi network, the fact that the device remains online, and packet timing while the keepalive remains armed. Depending on the network, the source IP can imply ISP, organization, travel state, or correlation between a device expected to be behind a VPN and a non-VPN access network.

7   Original
jello
programming.dev
jello@programming.dev
Joined: 2025-12-08
#2 Posted:   Subject: Re: Android NAT-T Keepalive Offload Bypasses VPN Lockdown: De... Quote Reply

Is this the thing that GrapheneOS fixed a while ago?

1
printf("%s", name);
piefed.blahaj.zone

akunohana@piefed.blahaj.zone
Joined: 2026-03-30
#3 Posted: · edited   Subject: Re: Android NAT-T Keepalive Offload Bypasses VPN Lockdown: De... Quote Reply

Is this the thing that GrapheneOS fixed a while ago?

No, GOS is currently working on a solution, while AOSP simply rejected and closed the issue without action.

3
Post Reply Page 1