Skip to main content

Cafe Crack – Instant Man in the Middle

Things like this[1] make me wonder how we’ll even get some semblance of sanity over the security and identity protection of mobile users.
Cafe Crack, provides a platform built from open source software for deploying rogue access points and sophisticated Man-in-the-Middle attacks.
They make it look easy:
Using only a laptop, the attacker can sit unassumingly in a public location to steal personal information. Perhaps the most alarming aspect of this demonstration is that it was accomplished with only a laptop and existing open-source software.
I knew it could be done, but I thought it was harder than that.
There are things that corporations can do, like spin up VPN’s:
However, the good news is that it is just as easy to protect oneself against Man-in-the-Middle attacks on an unsecure wireless connection. By using DNSSEC or VPN services, the user can bypass the attacker and keep their information secure.
But for ordinary users?
In the end, it is up to the user to be knowledgeable and safe around unsecure technology like public wireless.
I think ordinary users don’t have a chance.

Update (07/06/2012): The FBI warned on this type of attack..

[1] Cafe Cracks: Attacks on Unsecured Wireless Networks, Paul Moceri and Troy Ruths

Comments

  1. I make it a point never to ever connect to an ad hoc network. That cuts down 95% of the mitm risks, at least, I think it does.

    Good information to have though, and I think you're right. Most people don't stand a chance

    ReplyDelete
  2. Matt - I don't see why the bad guy can't emulate an infrastructure access point and broadcast an SSID that appears to be related to nearby businesses.

    I'd fall for it.

    ReplyDelete
  3. I've been to too many coffee shops where the shared access point was an UNCONFIGURED WiFi router. Every time I have ever spotted one, I have connected, tried the default password, and gotten in. It would take all of five minutes to hide the original router, connect my computer to it, then 'share' the connection with the original router's name.

    And Michael's trick would work. Especially at the marginal range, where you could 'extend' an open network, without interfering with the original. "Oh, look! I can connect to Starbucks from here!"

    You could probably do this with a netbook (or even a tablet), and not even dig it out of your backpack.

    ReplyDelete

Post a Comment

Popular posts from this blog

Cargo Cult System Administration

“imitate the superficial exterior of a process or system without having any understanding of the underlying substance” --Wikipedia During and after WWII, some native south pacific islanders erroneously associated the presence of war related technology with the delivery of highly desirable cargo. When the war ended and the cargo stopped showing up, they built crude facsimiles of runways, control towers, and airplanes in the belief that the presence of war technology caused the delivery of desirable cargo. From our point of view, it looks pretty amusing to see people build fake airplanes, runways and control towers  and wait for cargo to fall from the sky.The question is, how amusing are we?We have cargo cult science[1], cargo cult management[2], cargo cult programming[3], how about cargo cult system management?Here’s some common system administration failures that might be ‘cargo cult’:Failing to understand the difference between necessary and sufficient. A daily backup is necessary, b…

Ad-Hoc Verses Structured System Management

Structured system management is a concept that covers the fundamentals of building, securing, deploying, monitoring, logging, alerting, and documenting networks, servers and applications. Structured system management implies that you have those fundamentals in place, you execute them consistently, and you know all cases where you are inconsistent. The converse of structured system management is what I call ad hoc system management, where every system has it own plan, undocumented and inconsistent, and you don't know how inconsistent they are, because you've never looked.

In previous posts (here and here) I implied that structured system management was an integral part of improving system availability. Having inherited several platforms that had, at best, ad hoc system management, and having moved the platforms to something resembling structured system management, I've concluded that implementing basic structure around system management will be the best and fastest path to …

The Cloud – Provider Failure Modes

In The Cloud - Outsourcing Moved up the Stack[1] I compared the outsourcing that we do routinely (wide area networks) with the outsourcing of the higher layers of the application stack (processor, memory, storage). Conceptually they are similar:
In both cases you’ve entrusted your bits to someone else, you’ve shared physical and logical resources with others, you’ve disassociated physical devices (circuits or servers) from logical devices (virtual circuits, virtual severs), and in exchange for what is hopefully better, faster, cheaper service, you give up visibility, manageability and control to a provider. There are differences though. In the case of networking, your cloud provider is only entrusted with your bits for the time it takes for those bits to cross the providers network, and the loss of a few bits is not catastrophic. For providers of higher layer services, the bits are entrusted to the provider for the life of the bits, and the loss of a few bits is a major problem. The…