Somebody did an interesting attack on a cable network's customers.
They cracked the cable company's DHCP server, got it to provide a
"Connection-specific DNS suffic" pointing to a machine they owned,
and also told it to use their DNS server.
This meant that when your machine wanted to look up,
it would look up instead.

This looks like it has the ability to work around DNSSEC.
Somebody trying to verify that they'd correctly reached
would instead verify that they'd correctly reached, which can provide all the signatures
it needs to make this convincing.

So if you're depending on DNSSEC to secure your IPSEC connection,
do make sure your DNS server doesn't have a suffix of

------------------------------ RISKS-LIST: Risks-Forum Digest Saturday 17 June 2003 Volume 22 : Issue 78 ------------------------------ Date: Fri, 20 Jun 2003 15:33:15 -0400 From: Tom Van Vleck <[EMAIL PROTECTED]> Subject: ISP's DHCP servers infiltrated

"... It turns out, Charter Communications' DHCP servers were
infiltrated and were providing as the
'Connection-specific DNS suffix', causing all non-hardened Windows
(whatever that means in a Windows context) machines to get lookups
from a hijacked subdomain DNS server which simply responded to every
query with a set of 3 addresses (,,

On these IPs were some phantom services. There were proxying Web
servers (presumably collecting cookies and username/password combos),
as well as an ssh server where the perpetrators were most likely
hoping people would simply say 'yes' to the key differences and enter
in their username/password..."

Hmm, my cable ISP was down this morning. Maybe coincidence.

The Cryptography Mailing List
Unsubscribe by sending "unsubscribe cryptography" to [EMAIL PROTECTED]

Reply via email to