Slashdot Mirror


Public Access 'Blackspots'

WeakGeek writes "Unstrung has a story talking about a security issue with the combining of 802.11 and GSM/GPRS networks. Seems that 802.11b hotspots provide hackers with an easy way to grab user information from the wide-area network itself. Back when GSM was being defined, standards were designed to only authenticate the details held on the SIM card in a user's device before starting a session on the network. The user's device doesn't in turn check the credentials of the network. Fake a network, get data. Of course, the linked to story seems to be a 'viral' advertisement for a product that fixes this, but I still thought it interesting enough to share."

89 comments

  1. WEP by dextr0us · · Score: 0, Interesting

    if i recall.... WEP is the wirless encryption protocol. 802.11 networks should be rolling it out if its not already. Simple solutions? use an SSL gateway

    --
    "Martha Stewart can lick my Scrotum......do i have a scrotum?" -- Sharon Osbourne
    1. Re:WEP by GigsVT · · Score: 1

      WEP supposedly stands for "wired equivalent privacy", but in reality it is no where close, so your definition may as well be what it stands for.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    2. Re:WEP by monkey_tennis · · Score: 1

      WEP encrypts data in transit, but it requires all users to use the same key, so user authentication has to be done at a higher (application) level. Fine for SOHO use, but no good for corporates or people selling access to networks :)

    3. Re:WEP by Anonymous Coward · · Score: 1, Interesting

      I may be a bit hazy on how the authentication works, but if the phone connects to some system to verify the key that the network sends is good, will it connect through the network it's trying to verify?

    4. Re:WEP by esquimaux · · Score: 4, Informative

      Great acronym-dropping, but I'm afraid you have no idea what you're talking about. In a vanilla WEP implementation, all users have to know the shared key of the network, which means that any user has sufficient knowledge to masquerade as the network itself. More modern schemes, like Cisco's, allow the network to authenticate itself to the user (and vice versa), and then provide a per-user key. This prevents the sort of deception (poorly) described in the article.

      "SSL Gateway"? SSL doesn't have anything to do with it. Do you mean IPSEC, or some other tunnel-based security? Or do you mean encapsulating GSM traffic within an SSL connection? That's not exactly a simple solution.

      -- Robert

    5. Re:WEP by QuadGoatBoy · · Score: 5, Informative

      No, WEP stands for Wireless Equivalent Privacy, and it certainly has nothing to do with good encryption (uses RC4). What the WEP tries to (poorly) gaurantee is that clients are authenticated with the access point, server, whatever. Unfortunately, it is a one-way authentication that only validates the client, not the access point or server. What that means is that if you get a rogue access point with a bigger signal than the legitimate access point, the client will authenticate with the rogue access point, giving away passwords, encryption keys, etc. Throw in the fact that most wireless networks use shared keys, and you have just set yourself up for a security disaster. SSL gateway will not really help you if you have a man in the middle attack. If the man in the middle can grab the authentication key, it can masquerade as a legitimate user and possibly find out even more great things. If you want more info, check out "Wireless Network Security" published by the National Institute of Standards and Technology and the Department of Commerce. As far as encryption goes, WEP even gives away 24 bits of the encryption key with the IV (Initialization Vector). If you want a good list of the problems with wireless, check out section 3.3.2 of the document I mentioned. If you'd like a checklist of things you can do to lessen your security risks with wireless, check out sections 3.8 and 3.9. Of course, they include things like eye scanners and fingerprint scanners to even access a room with wireless capabilities, but most of those recommendations can be implemented by small to medium businesses with small amounts of technology capital. Thank you for your time, Quadgoatboy

    6. Re:WEP by argmanah · · Score: 2, Informative

      The idea of WEP is to encrypt transmission between the wireless device and the base station. It's mainly just to make sure the traffic doesn't get hijacked in transit, it's very poor as a true authentication scheme. WEP is about as secure as an unlocked car. Click here for a technical explaination of why, plus here for the application that actually does it.

      --
      Overrated Moderation: This posts sucks... because.
    7. Re:WEP by gylle · · Score: 1

      > WEP stands for Wireless Equivalent Privacy
      It most certainly does not. WEP stands for Wired Equivalent Privacy

    8. Re:WEP by QuadGoatBoy · · Score: 1

      Actually, you are correct. My bad. It does stand for Wired Equivalent Privacy.

    9. Re:WEP by esquimaux · · Score: 1

      There's nothing terribly wrong with RC4. I hate to see its good name sullied like this. It's cheap, well-understood, and widely implemented. If you're accessing a web page with SSL/TLS, you're probably using the RC4 cipher.

      As you say, the major problem with WEP's use of RC4 was in the selection of weak IV's. The other major issue was in key management. If long-lived, shared, static keys are replaced with short-lived, individual keys for unicast traffic, the security of WEP is greatly enhanced.

      -- Robert

    10. Re:WEP by QuadGoatBoy · · Score: 3, Informative
      Not quite. RC4 has several pretty serious flaws, both in design and popular implementation. Do you remember when it single-handedly rendered SSH1 useless?

      http://www.ipsec.co.jp/products/ssh/cert/vulnerabi lity.html

      Here is an even cuter, step-by-step explanation of how to BRUTE-FORCE CRACK the IV and RC4 encryption in less than 1 MINUTE!

      http://www.dachb0den.com/projects/bsd-airtools/wep exp.txt

      and the author even provides you with some auditing tools... for your network of course!

      http://www.dachb0den.com/projects/bsd-airtools.htm l

      Padding your keys with any number, especially zero, is not a good encryption scheme. Did I mention that RC4 calls for this? It did wonders for the Windows password file. LOL!

      http://etudiant.univ-mlv.fr/~ecorreia/toto.html

      Want more examples? Email me. It's just not a good algorithm. Unless under some kind of special condition, AES, Blowfish, or something else should be used instead.

      Thank you for your time,

      Quadgoatboy

    11. Re:WEP by RupW · · Score: 1

      Came across this in my metamod list. Obviously I'm not an RSA customer so all I know about RC4 is from Schneier.

      Not quite. RC4 has several pretty serious flaws, both in design and popular implementation.

      What are the design flaws? I've never heard of any. It's a neat, simple stream cipher with a ridiculuously long cycle. I can't remember if you can prove there's only a single cycle or not.

      Implemenation - there's no reason to bash RC4 because it's been used in a bad protocol. Skimming your links it looks like any stream cipher would have had the same problem. Or any block cipher, including AES, if they'd used dropped it in in CFB mode using the same IV, etc.

      Padding your keys with any number, especially zero, is not a good encryption scheme. Did I mention that RC4 calls for this?

      No, you repeat the key to get 256 bytes, i.e. from "ABCD" you'd use "ABCD" 64 times rather than "ABCD" then 252 zeros.

    12. Re:WEP by QuadGoatBoy · · Score: 1
      Agreed, on the padding. Misunderstanding of a couple texts I came across.

      However, RC4 has had some setbacks recently.

      A paper on attacking RC4
      A more theoretical attack paper
      A paper describing an attack that requires some guessing and probability theory

      I have a few problems with the RC4 algorithm, only one of which I'll talk about. It's not implemented poorly in one or two protocols, but several. If it's that hard for engineers to implement properly, then my brain simply thinks "Don't use that protocol! It's not worth it!" Perhaps, it's an okay protocol. Perhaps, there are just too many engineers that don't know how to implement it properly.

      Thank you for your time,

      Quadgoatboy

      P.S. As a side note, I don't know about you, but I just don't trust a protocol that padds itself 64 times on a 32 bit key. That just kind of... creeps me out :D. Yeah, yeah, I'm paranoid, but isn't anyone who uses encryption.

  2. Cellular technology, here we come! by t0ny · · Score: 0
    All right! Welcome back to the days of cloning! Its amazing- I may as well dust off my old motorola brick phone.

    I guess the good thing is that not many phones are 802.11 capable. The amazing thing is that with 802.11 being so insecure that anyone would think adding this feature would be a good idea.

    --

    Manipulate the moderator system! Mod someone as "overrated" today.

  3. oh? by Joe+the+Lesser · · Score: 3, Funny

    'This all adds up to networks that could be vulnerable to hacker attacks, according to Schlumberger.'

    What an amazing conclusion. Networks are vulnerable. Thank you once again, Captain Obvious.

    --
    "I only speak the truth"
    Karma: null(Mostly affected by an unassigned variable)
    1. Re:oh? by monkey_tennis · · Score: 2, Informative

      Actually it's even more obvious than that: WLAN networks are vulnerable "because it's cheap to get a base station and masquerade as a network".

      True, but frankly missing the point by a mile... Commercial WLANs need rock solid authentication for both ends for billing, trust, access control etc. etc.

    2. Re:oh? by Anonymous Coward · · Score: 0

      Networks are vulnerable. Thank you once again, Captain Obvious.

      Um, are networks vulnerable by definition? I think not. How do you know it's vulnerable if all you know is that it's a network?

  4. Vulnerable networks by knightinshiningarmor · · Score: 4, Funny

    from the article:

    This all adds up to networks that could be vulnerable to hacker attacks

    All networks are vulnerable, no matter how many precautions you take. Heck, just watch mission impossible again (if non-networked computers are vulnerable,...).

  5. Great by Hex4def6 · · Score: 2, Insightful

    ...However, for public wireless LAN implementations that will connect to backend systems on GSM and GPRS networks, Schlumberger has developed a SIM card-based system (surprise!) that enables mutual authentication between the device and ... ... It's hardly "viral marketing" when you don't promote the product, but just mention that's its one of the solutions to the problem.

  6. More good reading by Gortbusters.org · · Score: 4, Informative

    If ya don't read the article, check out WLAN: The Four S's, and a WEP FAQ.

    --
    --------
    Free your mind.
  7. What blackspots ? by MosesJones · · Score: 3, Interesting


    And why would 802.11b fix this ? If you can put 802.11b there why not just put up a cell to fix the problem ?

    Right now where are the 802.11b networks... for the most part they are in the cities. Where do you not have a problem with reception... in the cities.

    Why would someone put an 802.11b network out on Route 100N in Vermont rather than just a cell on the top of the mountain ? I'm obviously Mr Thicky here as it does seem that if you are going to put up a wireless network you might as well put up one that is already supported by phones rather than adding more bulk to the phones with a seperate set of chips to drain the battery.

    I've got bluetooth on my mobile, and GPRS. Someone please tell me why I'd want 802.11b as well ?

    --
    An Eye for an Eye will make the whole world blind - Gandhi
    1. Re:What blackspots ? by Anonymous Coward · · Score: 5, Interesting

      The answer is quite simple actually. If the phone could support a protocol with a cheaper infrastructure, then implementing the protocol might not be a bad idea. Say for example that you have an A band PCS network (1850->1945 MHz). The network has great outdoor coverage, but the in-building penetration at PCS frequencies is weak. A large buisness customer wants better coverage inside their offce, but doesn't want to foot the bill for a new $70,000+ base station, never mind trying to get FCC/FAA approval or a lease. Instead, using the network infrastructure that already exists inside the building you add 802.11 access points in places where coverage is weak. Voila, you've managed to solve the problem for probably less that $5,000. There are of course problems with smooth handovers between the 802.11 part of the network and the GSM part of the network, but that's a whole other kettle of fish.

    2. Re:What blackspots ? by nyssa · · Score: 1

      I've got bluetooth on my mobile, and GPRS. Someone please tell me why I'd want 802.11b as well ?

      Two reasons:

      • More bandwidth
      • Less expensive air-time charges
  8. It's okay ... by snack-a-lot · · Score: 1

    ... it uses 3G, and is therefore not popular enough to be an immediate serious concern (unlike, for example, hacker attacks on products like Outlook, which are used by millions)

  9. What's this to do with GSM? by monkey_tennis · · Score: 3, Interesting

    Maybe I'm missing the point :) but isn't this just a function of the fact that there is no user-level authentication in 802.11b at all... The fact that this makes it difficult to hook up WLANs to GSM networks is only just a side-effect.

    Doesn't 802.11x begin to address this?

    1. Re:What's this to do with GSM? by Beatbyte · · Score: 2, Informative

      Yes you are missing the point. Read the article.

      "The heart of the problem is that when the GSM standard was being defined back in the late 80s, no one imagined that a hacker could set up his own wireless network to gain access to an operator's network and the user data therein. Therefore, GSM networks only authenticate the details held on the SIM card in a user's device before starting a session on the network. The user's device doesn't check the credentials of the network it is attempting to access.

      This was fine before the advent of wireless LAN. But now for a minimal outlay anyone can own a wireless network.

      Hackers can set up "rogue" hotspots that users will access in the belief they are on the genuine public wireless LAN network. Once users are on the fake network, it is easy for the hacker to access data held on the device via the 802.11 connection (see WLAN: The Four S's and this paper for more on the insecurity of wireless LAN). Hackers can then break into the SIM software on the user's device and get the codes held there. They can then use that information to fool the GSM authentication system and thus gain access to the network."

    2. Re:What's this to do with GSM? by monkey_tennis · · Score: 1

      My point exactly - 802.11 doesn't have any user authentication meaning that neither party can trust the other. Stealing information to allow you to then access a GSM network is no different to a rogue access point stealing my credit card info off my laptop.

      I did read the article - did you understand it?

    3. Re:What's this to do with GSM? by Anonymous Coward · · Score: 0

      Sure, but there isn't many cell phones with wireless LAN.

    4. Re:What's this to do with GSM? by nyssa · · Score: 1

      This becomes an issue when you use your GSM SIM card to authenticate access to a WiFi hotspot that is affiliated with your GSM network service provider. This is part of a scheme to provide seamless roaming between GSM/GPRS and WiFi.

      My understanding of the problem is that when you access a hotspot that you think belongs to AT&T (or whoever your GSM service provider is) but it actually is a counterfeit, the rogue hotspot can glean information from your SIM card that would enable them to hack into the AT&T GSM network.

  10. The complete story by ftvcs · · Score: 5, Informative
    Public Access BlackSpots?
    02.21.03

    CANNES, France -- 3GSM Congress -- There's a big problem with connecting public wireless LAN access points to GSM/GPRS cellular networks, according to SIM card vendor SchulmbergerSema. 802.11b hotspots provide hackers with an easy way to grab user information from the wide-area network itself, the company tells Unstrung.

    The heart of the problem is that when the GSM standard was being defined back in the late 80s, no one imagined that a hacker could set up his own wireless network to gain access to an operator's network and the user data therein. Therefore, GSM networks only authenticate the details held on the SIM card in a user's device before starting a session on the network. The user's device doesn't check the credentials of the network it is attempting to access.

    This was fine before the advent of wireless LAN. But now for a minimal outlay anyone can own a wireless network.

    At the same time, vendors and operators are starting to use SIM card-based authentication front-end systems for public wireless LAN networks, which allow them to link the user back to the home location register (HLR) database on the GSM network and thus manage and bill a subscriber on the WLAN network in the same way as they would on the wide-area network.

    This all adds up to networks that could be vulnerable to hacker attacks, according to Schlumberger.

    Hackers can set up "rogue" hotspots that users will access in the belief they are on the genuine public wireless LAN network. Once users are on the fake network, it is easy for the hacker to access data held on the device via the 802.11 connection (see WLAN: The Four S's and this paper for more on the insecurity of wireless LAN). Hackers can then break into the SIM software on the user's device and get the codes held there. They can then use that information to fool the GSM authentication system and thus gain access to the network.

    Schlumberger say that this won't be a problem once UMTS networks are available, because the 3G standard ensures what's known as "mutual authentication" -- the network authenticates a user device, and the device confirms that it is actually on a valid network before the session can proceed.

    However, for public wireless LAN implementations that will connect to backend systems on GSM and GPRS networks, Schlumberger has developed a SIM card-based system (surprise!) that enables mutual authentication between the device and networks that are accessed via the gateway of public wireless LAN hotspots. The mutual authentication takes place via algorithms on the card itself rather than in SIM card software on the device.

    Schlumberger is showing a system at the 3GSM congress that uses a separate smartcard and reader plugged into a WLAN-enabled laptop. However, the firm says that the smartcard and radio could be integrated into one PCMCIA card, much in the way that Nokia Corp. (NYSE: NOK - message board) has done.

    Orange France is currently testing Schlumberger's security system. Schlumberger expects that operators will start to roll it out before the end of this year.

    -- Dan Jones, Senior Editor, Unstrung
    http://www.unstrung.com

  11. ICH WEISS, DA� SIE NICHT VERSTEHEN by YOU+ARE+SO+FIRED! · · Score: 0, Informative

    Ich spreche nicht wirklich Deutsch. Versuch, für eine Amerikanische Firma zu arbeiten, damit ich Amerikaner zu Ihnen sprechen kann. Dann werde ich Sie brennen. Geschäft?

    1. Re:ICH WEISS, DA� SIE NICHT VERSTEHEN by Anonymous Coward · · Score: 0

      *BSD sucks. And it's dead.

  12. 802.11b WAN will be shortlived by mattyohe · · Score: 4, Interesting

    With the absence of FCC police in a metropoliton area, enforcing the laws of power usage and whatnot is becomming impossible. Ofcourse you can submit a complaint but good luck having an offical actually come out and survey the damage, and while adding all of these cell phones to the mix sounds like a fun idea, its only going to cause many many problems. Why can't these hotspots be using a liscensed freq instead of publicly avaialble one? Especially now that the hams finally realised that they can use the 2.4ghz spec for data. Thats also an odd situation... The hams were way behind on the 2.4ghz issue.. they have had it available forever but was slow to catch on.. With all of these 2.4 freq. products, in a couple years we will be glowing green from all of the radiation.

    Why don't we just install it under our skins and we can all be 802.11 hotspots ourselves.

    --
    - what is the definition of simultanagnosia?! I've been meaning to look it up!
    1. Re:802.11b WAN will be shortlived by GigsVT · · Score: 2, Informative

      Hams always knew we could use 2.4Ghz at whatever power level we wanted. It's just that when transmitting in a ham capacity, life is pretty boring. You have to identify your station every 10 minutes, you can't transmit anything "obscene", you can't conduct any commercial business, etc. In other words, ham 2.4Ghz can't really ever be used for Internet access.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
  13. Re:*BSD... by Anonymous Coward · · Score: 0

    In Soviet Russia, "*BSD is dying" troll is too lazy to cut'n'paste YOU!

  14. A viral advertisement by Chester+K · · Score: 3, Funny

    Of course, the linked to story seems to be a 'viral' advertisement for a product that fixes this

    You guys need to fact check a bit. I didn't see anywhere that mentioned that the story was under the GPL.

    --

    NO CARRIER
  15. Tired of the wirless security fud by codepunk · · Score: 0, Flamebait

    I am constantly being asked if wireless networks are secure.

    Customer: Is this wireless networking secure?
    Me: What Operating System are you running?
    Customer: Windows Xpeee
    Me: It doesn't matter you will never be secure.!

    It is a matter of choice it can be as secure as you wish it to be. If you really think you need security tunnel through ssl..

    --


    Got Code?
    1. Re:Tired of the wirless security fud by secolactico · · Score: 1

      LOL!!! If I told that to a customer, I would be out of the door by the end of the day!

      Customer: Is this wireless network secure?
      Me: What OS are you using?
      Customer: WinXP
      Me: It doesn't matter, you will never be secure!
      Customer: *YOUR* job is to make me secure!
      Me: Unless you agree to let me change your OS that's not going to be possible. I can't perform miracles.
      Customer: I want to talk to your supervisor!

      time passes ...

      Supervisor: I had a complaint today. Please clean up your desk.

      Sucks to be me... at least I'm not in customer service anymore.

      --
      No sig
    2. Re:Tired of the wirless security fud by drakewyrm · · Score: 1

      Some people will do almost anything to avoid listening to the truth.

      "La. La. La. My machine is secure. La. La. La."

      --
      Batou: Hey, Major... You ever hear of "human rights"? Major: I understand the concept, but I've never seen it in action
  16. Bluetooth... by MosesJones · · Score: 1


    Could do that inside an office, very cheap and already on lots of phones. Blue tooth hardware can be tiny in comparison to 802.11b. And covers small blackspots like in offices.

    802.11b would be for bigger blackspots which begs the same question.

    --
    An Eye for an Eye will make the whole world blind - Gandhi
  17. Re:*BSD... by Anonymous Coward · · Score: 0

    *BSD sucks.

  18. Re:dat is niet correct by Anonymous Coward · · Score: 0

    Each year, the Institute for Comparative Troll Studies publishes a report on the state of trolling vis a vis national security of the United States. This year, the outlook is not good.

    Although the US posesses superior trolling to Iraq, the very focus on this disparity is part of the problem. Husseins skills are perhaps at the bottom of the troll-ladder of the world. 100% votes, 'the mother of all battles', etc, are not good trolls. All they do is get him laughed at. Nobody says 'by gum, he is right'.

    North Korea, however, points to a problem. North Korea 'stunned the world' by announcing it had nukes, a good troll. Unsuspected, got lots of press coverage, and caused dozens of front page articles on various magazines in the US. Even Hussein, whom the US is about to murder, has not gotten as much coverage as Kim Jong-Il. One would think the stereotype cartoonist factories have gone quiet, with the sheer lack of creativity devoted to lampooning Iraq in recent months.

    North Korea is now saying that it has the right to pre-emptively attack the United States. Again, this is a pretty good troll. It simulatneously pisses people off and unbuttons their hypocrisy: the US is at the very moment trying to push forward a 'pre-emptive strike' philosophy of modern warfare: this theory has not been all that popular in the US, a nation in which children routinely justify attacks by saying 'he/she hit me first'. Again, North Korea could hardly have chosen a better subject or time to troll the world with this idiom.

    But it doesn't stop there. Recently a German government official conformed to Godwin's Law and called the US leaders somewhat like Hitler. Maybe this is an urban out-of-context legend, but it doesn't matter if you are trolling, does it? The fact that it is from the same country that birthed the Nazis makes this a particularly sticky and annoying troll in the minds of the USian reader.

    On the US side, we have basically been scattered. Our Trolls are lacking in quality and skill. People like Rush Limbaugh, Sean Hannity, Michael Savage, CNN, Crossfire, Bill O'Reilly, Jon Stewart, Arianna Huffington, etc, they simply do not stack up to this new breed of trolling from across the oceans.

    I am not quite sure how to explain this. Perhaps the US has gotten lazy from having life too easy. Limbaugh et al are unfocused, unsure of themselves, and ignorant of the fundamentals of trolling. They lack historical background knowledge, and they fail to comprehend the motivations of the 'liberals' they tirade against. Huffington and whatnot are disconnected from the masses and unable to coalesce their vast mounds of facts about what is wrong with the conservatives into any kind of emotional climax. Their comments routinely fail to make world headlines.

    American government officials like Colin Powell fail to understand trolling completely. In his simplistic view of the world, all that matters are facts and figures and slow deliberate explanation: a ludicrous proposition in any age, especially when you completely fail to produce any facts and figures to refute your most virulent opponents. Ordinarily use of facts can destroy an opponent troll, but silence never will.

    His hangers on, Bush, Cheney, etc, are so completely devoid of life accomplishment or moral character (a couple DUIs, coke heads, frat boys, etc) that their lame attempts at trolling lose all credibility.

    I think the US needs to implement a troll retention program, troll development and training programs, and various other troll technology that will enable it to compete in the 21st century international troll arena. Otherwise, we are just so many hot grits down the pants of history.

  19. Re:dat is niet correct by Anonymous Coward · · Score: 0

    How do you say "*BSD users are braindead" in German?

  20. Helpful hint for moderators: by Anonymous Coward · · Score: 0, Informative
    1. Annonymous Cowards always post with a starting score of 0.
    2. Most slashdot readers not interested in the trolls set their threasholds to 1 or greater, thereby never seeing Annonymous Coward posts that haven't been modded up.
    3. That moderation point could have been used to mod a good post up.
    4. ?????
    5. Profit!
  21. just hire a HACKER! by puzzled · · Score: 1


    It is amazing how much of this stuff goes on in design - if the executives of the firms involved in the standardization process can't understand the problem, it must not exist!

    Every protocol out there is going to get picked apart ... by people like me :-) If you're designing a wireless product today, get a real live hacker to look at it from the minute you put pen to paper - if you don't design it secure, you can't go back and retrofit security later - one has to look no further than the 802.1X bag on the side of 802.11b.

    --
    I am very easy to get along with, but I don't have time to waste being nice to people who are being stupid. -Theo
  22. He wouldn't know by Anonymous Coward · · Score: 0

    As thats Dutch, not German.

  23. Tunneling GSM authentication not mentioned by eggboard · · Score: 3, Interesting

    Interestingly, nobody in the article or here mentions the fact that there's a very active group at the IETF that's working on securing all kinds of authentication messaging systems, including EAP (the method for 802.1x wired/wireless authentication). EAP is the focus, but the papers presented at the various conferences cover many authentication methods and methods of securing them.

    Protocols like EAP (Extensible Authentication Protocol) are intended to provide a generic mechanism over any transport system to handle legacy and modern handshaking and exchange to authenticate a user in a system.

    In 802.1x/EAP, included as of the 802.11i wireless security update, 802.1x defines the roles of a client, access point authentication passthrough, and an authenticator. 802.1x restricts access to the network until the access point using EAP has been told by the authentication system that the client is okay to be on the network. It hands off a key, which eliminates spoofing, as even if you spoof the MAC address, you don't have the key. The key can be swapped frequently, like every 10,000 packets.

    The problem with 802.1x/EAP is the same as with the SIM/GSM authentication system as described here. The authentication is sent in the clear! So you have three flavors of tunneled, SSL-like EAP: EAP-TLS (requires a pre-installed certificate on the client), EAP-TTLS (Meetinghouse, Funk support, tunnels EAP inside a tunnel), and PEAP (Microsoft, Cisco, same tunneling but ignores legacy protocols supported within EAP-TTLS).

    --
    Freelance tech journalist for the Economist, MIT Technology Review, Macworld, and others
  24. Hard to use this to clone mobiles. by threeturn · · Score: 5, Informative
    As someone who's worked on specifying the GSM standard since the early 90s (if not quite the 80s) I can shed some light on this, and why its a non-story.

    The scenario is one where GSM operators use 802.11 to provide data-infill on their GSM networks, and reuse the GSM authentication mechanism over 802.11 to control access. The article is correct to point out that it would be relatively easy for someone to setup an 802.11 access point which pretends to belong to a GSM operator and requests GSM authentication information from connecting devices.

    However, this shouldn't be too big a problem. The GSM authentication mechanism is based on a shared secret key which is written in to the SIM card in a way that SHOULD be read-only. Once its written the key is used by the SIM to calculate a response to a challenge sent from the network. This authentication algorithm is chosen by the network operator, and should be a one way function (ie you can't analyse the challenge/responses to get the secret key). Therefore, the hacker with a false network could get a set of valid responses to a set of challenges, but if the authentication algorithm is correct he can't use this data to get the secret key and clone the SIM.

    The only comment I would make is that flaws have been discovered in the authentication algorithms used by some networks which potentially makes it possible to find the secret key if you have enough challenge/response data. However these algorithms are being replaced, and the computation is still quite heavy.

    To summarise: fake networks attacks aren't new. Using 802.11 just makes it easier. Its best to suppress fake networks by mutual autentication, but even if you don't do this it should still be impossible for the fake network to get enough data to clone a mobile. The main problem with fake networks is that they can intercept the content of communications very easily.

    1. Re:Hard to use this to clone mobiles. by Anonymous Coward · · Score: 0

      If you've got a network that can elicit valid responses to network-provided challenges in real time, you don't NEED to clone the SIM.

      Now that everyone and their mother is producing cell-phone/PDA/palmtop superboxes, how long will it take to build a hack that passes the challenge across the fauxnet to a clueless innocent?

  25. a technology from the late 80s by sublime99 · · Score: 1

    They mention in the article that GSM was developed in the late 80s and then implemented around the world through out the years. It is obvious they couldn't think of all these new technologies.. progress costs something...

    There will always be people that will try to break into something, so just work on ways to make it more secure.

    Step 1.) Remove all Microsoft products

  26. EAP-SIM by tengwar · · Score: 2, Informative
    It's not a problem. If you use 802.1x with EAP-SIM, you get mutual authentication from a standard SIM, but you need two or three exchanges of information. USIMs (for UMTS) can do mutual authentication in one pass, so there's lower latency - but it's not appreciably more secure in the WLAN context.

    Someone mentioned that the authentication information for EAP is passed in the clear. EAP-SIM is not vulnerable to replay attacks because it's a challenge and response method. In normal GSM authentication, the network decides on a random challenge RAND. The network and the SIM calculate a signed response SRES and a session key Kc. The user equipment sends back SRES and the network uses it to authenticate the SIM. This leaves Kc as a shared secret at each end. EAP-SIM uses the same triplet, and uses the multiple passes for mutual authentication (theres an Internet Draft for it at http://www.ietf.org). EAP-SIM can also supply the accumulated Kc's to be used as a session key for WEP. Ok, WEP has known problems, but because you can force re-authentication periodically you can avoid a black-hat accumulating enough packets to crack your session.

    BTW, Schlumberger aren't the only company offering "WLAN" SIMs - another company has been unsuccessfully lobbying 3GPP (the 3G industry standardisation body, who deal with WLAN/3G interoperation) with the same idea.

    1. Re:EAP-SIM by Anonymous Coward · · Score: 0

      If someone has access to your SIM, then they can
      create the triplets and store them offline. With
      these triplets its easy to act as if you are the
      network when you are authenticating someone. You
      have the RAND, SRES, Kc and you can respond to
      any challenge that the client sends you. The
      EAP-SIM draft also mentions such limitations.

    2. Re:EAP-SIM by tengwar · · Score: 1
      (Reference is to http://www.ietf.org/internet-drafts/draft-haverine n-pppext-eap-sim-09.txt, section 19.2)

      Yes, but RAND is 128 bits! Even if the SIM didn't have defences against multiple requests (which many do), that's 3.4e28 triplets to record. It isn't going to happen.

      More realistically, if an operator is using the COMP128 encryption algorithm, given physical access to the SIM, the secret key Ki could be cracked in which case you could make up the triplets. That's a real problem, but it's not peculiar to WLAN - it would allow cloning of generic SIMs for GSM use. The problem is that COMP128 was intended as an illustrative algorithm, not intended for production use. Wise operators either don't use it, or are replacing SIMs using it.

  27. I've done this before myself. by dissy · · Score: 3, Interesting

    Ive done this before in a way myself.
    It was just an exparement at the time because I was bored.

    I setup an oBSD box with wireless card in it not connected to any real network, but acting as an access point.
    It handed out seemingly public IPs (It was slightly off from the real IPs my network used)

    I did not use WEP on purpose, but set the network name to 'Private_GO_AWAY' (or some such message)

    It then ran honeyd and pretended to be a network of a few hosts.

    People looking for net access failed to get it, and most left it at that.

    Once someone attempted to open a connection to any of these fake IPs, my machine portscanned them back, fingerprinted the OS, grabbed banners from any service it found running, and logged this all with date/time/MAC/hardware brand/etc info.
    It also at that point started logging every packet that IP sent up until it left the wireless network.

    It was fun to watch people who actually tried to 'break in' over wireless.
    As i recal it was only about 5 people in a 6 month period, out of hundreds of people 'passing by' looking for net access.

    Only those 5 or so people do I have detailed logs on. (I didnt bother logging anything about the ones just wanting net access, other than the fact they requested an IP and when)

    If my signal is being broadcast out and they have full rights to do what they want with it, I feel the same is true for the replys from their wireless hardware to me :)

  28. Simple solution... by hpa · · Score: 1

    There is a simple solution for those that care: maintain a trusted IPSec gateway for yourself somewhere (perhaps where you keep your mail and so on) and then just use IPSec for all traffic.

    Encryption makes it practical to separate the service of connectivity from the service of trust, so an untrusted hotspot can be safely used for connectivity while still maintaining a trusted connection.

  29. Sorry... I miss the point. by Anonymous Coward · · Score: 0
    The article says

    here's a big problem with connecting public wireless LAN access points to GSM/GPRS cellular networks

    then it goes on

    802.11b hotspots provide hackers with an easy way to grab user information from the wide-area network itself, the company tells Unstrung

    Now. I put a WI-FI hotspot. This WI-FI hotspot is connected to somewhere else with the internet via GSM/GPRS.
    Now, How does it come that an Hacker, accessing the internet via this hotspot, can sniff the authentication details that the GPRS modem is sending to the other party? (Because this is what I understood)
    The GSM Wireless network is a different protocol from the Wi-Fi. Faking a GSM Network will need that you
    1. find an unregulated zone where to do your tests (or otherwise, hope that the telcos are unattentive to strange interfereces, usually this is the case, but in a monopoly-regime like here in Italy there is not enough room to joke on this...)
    2. build up your fake gsm network and try to access it with the stolen gsm (or snoop everyone's gsm access attempts)
    3. then steal the gsmcard/password combination

    If I understood well, how is this related to Wi-Fi?
    Or is this the problem of, "I put my pc with Wi-Fi online then hackers can access my system and if I have a GSM card then they will read what's inside?"... that's the same problem when you put yourself on a lan. If you really need Wi-Fi, you ought to put firewalls on all your Wi-Fi machines and use VPN. Or not use Wi-Fi at all...
    Comments?
  30. The Fallacy of Network Security by drakewyrm · · Score: 2, Interesting

    As was mentioned above, any network can be penetrated once physical access is obtained. Most network security is designed around the concept of trusted portions of the network; an attacker must either break through a firewall, gain control of a machine within the trusted portion of the network, or add a machine under his control to the network. Under 802.2 and related networking protocols, physical access is limited to a wire; to add a machine to the network, an attacker must at least be in the building. Under 802.11, physical access is anywhere within a certain range of a node. With the right equipment, this range can be extended considerably. Suddenly, that firewall isn't quite so effective.

    My opinion hasn't changed since the first time I read about 802.11: great, useful, whatever, but NOT TO BE TRUSTED. I have an 802.11 hub on my network, but it sits in the DMZ. Wireless users around the house can still get access to the Internet and some network services, but unauthenticated machines can't get into my happy safe zone. If I needed something like that, I could set up VPN to let my wireless machines become part of the safe zone. VPN uses much better authentication and encryption than 802.11, and VPN implementations can be easily patched as the protocol improves. AFAIK, VPN authentication would defeat the attack described above.

    --
    Batou: Hey, Major... You ever hear of "human rights"? Major: I understand the concept, but I've never seen it in action
  31. Mod this up. by Anonymous Coward · · Score: 0

    It's cynical, but not untrue.

  32. Not entirely true by jquirke · · Score: 1

    The GSM authentication comments are not entirely true.

    When the radio-connection has been established, the network sends a unique 128-bit key (RAND) to the MS (phone). The phone then uses the A3/A8 algorithm implementation, together with the RAND and an internal key stored only in the SIM (and the network's AuC) known as the Ki. This algorithm produces a 32-bit SRES (authentication check) and a 64-bit Kc (data encryption key).

    RAND is sent in an AUTHENTICATION REQUEST message, and the computed SRES is sent back in an AUTHENTICATION RESPONSE. The Kc is not returned (as the network already knows it, the SRES is sent to confirm that the MS is who it says it is).

    In theory, the attacker could ignore the response and begin an unciphered radio connection. However, ciphering forms an implicit form of two-way authentication. Since the Kc is used to encrypt calls, and the real Kc is not known by the network, the phone would start encrypting bursts (packets) and the network would not be able to decrypt them, hence communication would fail.

    Of course, the network could simply avoid encryption by specifying no algorithm in CIPERING MODE COMMAND message, however most phones would display a warning to the user that the session is not encrypted, and hence the attack is known.

  33. BTW by QuadGoatBoy · · Score: 1
    I just talked with an engineer who told me that padding is not even really a requirement of the RC4 or ARC4 algorithm, and that there are implementations of it, such as a nice 160 bit implementation, that use no padding whatsoever. I'm pleased with that description, and all such arguments against RC4 in my mind have subsided, especially since the truth of the matter on the implementation concerns is that no matter what algorithm was implemented in the situations I mentioned earlier, most of the holes would probably still have existed. Poor engineering is poor engineering.

    In other words, both of you are right, and I am wrong. Enjoy ;).

    Thank you for your time,

    Quadgoatboy

  34. Last Post! by alpg · · Score: 0

    The idea that an arbitrary naive human should be able to properly use a given
    tool without training or understanding is even more wrong for computing than
    it is for other tools (e.g. automobiles, airplanes, guns, power saws).
    -- Doug Gwyn

    - this post brought to you by the Automated Last Post Generator...