3 ms·
Wasn't it fixed long, long ago? As I remember, kernel developers were fixing TCP sequence numbers at some point.
by dozzie 10y ago
Wasn't it fixed long, long ago? As I remember, kernel developers were fixing TCP sequence numbers at some point.
- attilagyorffy 10y agoI vaguely remember something around a potential fix but I lost track of it. The strange thing is that this appeared yesterday. I haven't had time to actually test this, am just looking to see what the community knows, whether someone could confirm this.
- cjbprime 10y agoSomeone else has already linked to a fix that the Linux kernel developers applied, which tells us that it's a confirmed problem (at least in theory): https://git.zx2c4.com/linux/commit/?id=75ff39ccc1bd5d3c455b6822ab09e533c551f758 https://git.zx2c4.com/linux/commit/?id=75ff39ccc1bd5d3c455b6...
- jfindley 10y agoThere's been a few TCP sequence related vulnerabilities over the years, but this is slightly different - it's actually a problem with how ACKs are processed, making it far easier than it should be to conduct a well-known attack type (blind in-window). EDIT: it's of course still sequence related, but a new vuln, not a restarting of an older, fixed one.