News for hackers. Stuff that matters.
Re:Off-path TCP hijacking in NAT-enabled Wi-Fi networks by patrakov on Wednesday June 19, 2024 @03:55AM (#40725934)
The legit use case is to pick up connections that were established before the router reboot.
Re:Off-path TCP hijacking in NAT-enabled Wi-Fi networks by blahgeek on Wednesday June 19, 2024 @04:47AM (#40726223)
If the router reboots, it cannot remember the correct mapping of the last connection, right? (The mapped port may not be the original source port)
Re:Off-path TCP hijacking in NAT-enabled Wi-Fi networks by r1ch on Wednesday June 19, 2024 @06:20AM (#40726809)
That's why port preservation is the usual behavior.
Re:Off-path TCP hijacking in NAT-enabled Wi-Fi networks by patrakov on Wednesday June 19, 2024 @08:37AM (#40727683)
(edited) Correct, this pickup of ports from the ACKs that the internal host keeps resending only works if the externally mapped port didn't change from the default (same as internal).
Re:Off-path TCP hijacking in NAT-enabled Wi-Fi networks by semi on Wednesday June 19, 2024 @12:25PM (#40729756)
wouldn't it also work for connections established on another router that then failed or otherwise had traffic shift to it?