A TCP weakness in Linux systems allows network traffic hijack
1–10 of 25 posts
Re: A TCP weakness in Linux systems allows network traffic hijack
#2Re: A TCP weakness in Linux systems allows network traffic hijack
#3Re: A TCP weakness in Linux systems allows network traffic hijack
#4Wasn't it fixed long, long ago? As I remember, kernel developers were fixing TCP sequence numbers at some point.
Re: A TCP weakness in Linux systems allows network traffic hijack
#5Re: A TCP weakness in Linux systems allows network traffic hijack
#6Wasn't it fixed long, long ago? As I remember, kernel developers were fixing TCP sequence numbers at some point.
EDIT: it's of course still sequence related, but a new vuln, not a restarting of an older, fixed one.
Re: A TCP weakness in Linux systems allows network traffic hijack
#7Re: A TCP weakness in Linux systems allows network traffic hijack
#8I'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.
I'm proceeding on the assumption that it's real, and working towards ensuring everything (with a kernel >= 3.6 and 0: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5696 1: https://access.redhat.com/security/cve/cve-2016-5696
Re: A TCP weakness in Linux systems allows network traffic hijack
#9Re: A TCP weakness in Linux systems allows network traffic hijack
#10I'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.
The ISS Source article itself is garbage.
They do not explain the origin of the attack, instead simply mention "a subtle flaw (in the form of 'side channels')" [sic]. They do not explain why their "temporary patch" [sic] of raising the challenge ack limit makes the vuln "practically impossible to exploit".
Hell, they do not even link to the original paper.