A TCP weakness in Linux systems allows network traffic hijack

  • Apparently this command fixes the problem:

    echo 'net.ipv4.tcp_challenge_ack_limit = 999999999' >>/etc/sysctl.conf;sysctl -p

    I got this from http://www.isssource.com/fixing-an-internet-security-threat/ but they had a typo

  • Here's the commit for fixing this: https://git.zx2c4.com/linux/commit/?id=75ff39ccc1bd5d3c455b6...

  • Currently listed as vulnerable and unfixed in Debian: https://security-tracker.debian.org/tracker/CVE-2016-5696

  • What's interesting is that this is a protocol bug, not an implementation/software bug (in RFC 5961).

    It is intriguing to realize that the three information leakages are enabled by the three (and only three) conditions that trigger challenge ACKs...

    Indeed. It almost looks like an intentional back door.

  • I've found this on isssource and am surprised that it has not spread like wildfire. If the claims are true then this is an issue that should be taken seriously. Posting here for discussion.

  • Probably affects Android too since it uses the Linux kernel.

    Personally I consider this to be a mild to moderate vulnerability since under no circumstances should you ever trust a non-encrypted non-authenticated channel to be safe. TCP offers in-order delivery and decent integrity checking but otherwise offers absolutely no security guarantees at all. From a crypto point of view an authentication method like TCP sequence numbers should be considered "not even there."

  • This strongly reminds me that Silence on the wire by Michal Zalewski, really is an excellent read.

  • Wasn't it fixed long, long ago? As I remember, kernel developers were fixing TCP sequence numbers at some point.

  • Earlier today I had an issue where, for some reason, my IP address was wrong. Like I was being sent through a VPN. Google and IRC were treating me as if I had a spammer's IP address.

    I know this is a common virus issue on Windows but couldn't find any explanation for why that would happen on Linux and, after turning on my actual VPN, it went away.

    So could someone explain if this is related to me? I was seriously freaked out by it, and still don't really have an explanation.