full-disclosure - Re: TCP Hijacking (aka Man-in-the-Middle)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <32505.1193334053@turing-police.cc.vt.edu>
Date: Thu, 25 Oct 2007 13:40:53 -0400
From: Valdis.Kletnieks@...edu
To: Oliver <olivereatsolives@...il.com>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: TCP Hijacking (aka Man-in-the-Middle)

On Thu, 25 Oct 2007 10:09:47 PDT, Oliver said:

> I have been searching all over the place to find an answer to this question,
> but Google has made me feel unlucky these last few days. I hope I could find
> more expertise here. The burning question I have been pondering over is -
> could TCP connections be hijacked both ways?

Quick summary:

Steve Bellovin pointed out the issue. 19<stone age>

Kevin Mitnick exploited it. 19<bronze age>

Steve wrote RFC1948, which basically said "Use randomized ISNs so the attacker
has to work harder at it". 1996.

A lot of vendors sort of implemented it. 1996-2000.

Michael Zalewski did a nice phase-space analysis and showed a lot of vendors
botched it. http://lcamtuf.coredump.cx/oldtcp/tcpseq.html 2000

A lot of vendors fixed their shit, but a lot didn't.
http://lcamtuf.coredump.cx/newtcp/ 2001.

You're now caught up to 6 years ago.

Content of type "application/pgp-signature" skipped

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/