Slashdot Mirror


MacBook Wi-Fi Hijack Details Finally Released

Wick3d Gam3s writes "Hacker David Maynor attempted to put the strange tale of the Macbook Wifi hack to rest, and offered an apology for mistakes made. All this and a live demo of the takeover exploit was made at a Black Hat DC event yesterday. Maynor promised to release e-mail exchanges, crash/panic logs and exploit code in an effort to clear his tarnished name. Said Maynor: 'I screwed up a bit [at last year's Black Hat in Las Vegas]. I probably shouldn't have used an Apple machine in the video demo and I definitely should not have discussed it a journalist ahead of time ... I made mistakes, I screwed up. You can blame me for a lot of things but don't say we didn't find this and give all the information to Apple.'"

27 of 82 comments (clear)

  1. Crash? I thought the original claim was... by bluemonq · · Score: 3, Insightful

    ...that he could gain complete access over the machine? Frankly, I wouldn't even be surprised if he did some old-fashioned reverse-engineering of the patch to create the exploit for the older boxes.

    1. Re:Crash? I thought the original claim was... by DJCacophony · · Score: 2, Informative

      Frankly, I wouldn't even be surprised if he did some old-fashioned reverse-engineering of the patch to create the exploit for the older boxes.

      And then used his time machine to go back in time to before the bug was patched and announce the exploit?
      The guy informed the world about the bug, then Apple fixed it, but refused to credit him for it.

      --
      Slow Down, Cowboy! It's been 60 minutes since you last successfully posted a comment.
    2. Re:Crash? I thought the original claim was... by Rosyna · · Score: 4, Interesting

      Frankly, I wouldn't even be surprised if he did some old-fashioned reverse-engineering of the patch to create the exploit for the older boxes.

      And then used his time machine to go back in time to before the bug was patched and announce the exploit?


      No, his original claim was a farce (hell, look at the video, there was only one wireless device available according to ifconfig). Apple then audited their code, found 3 bugs. He took one of the bugs mentioned, found out how to trigger it, triggered the crash and now claims he was right all along.

      The problem is that what's happening now doesn't support his original claims. The original claims were he could hijack a MacBook in under 60 seconds and gain completely control of it. Now all he's getting is a crash with no control.

    3. Re:Crash? I thought the original claim was... by AchiIIe · · Score: 5, Interesting

      That is correct, the original video was faked... They prob were close but did not want to wait.
      Here is a video I made debunking their proof: http://video.google.com/videoplay?docid=1468187717 11399295&hl=en
      My guess is that they got a buffer overflow but had not yet found the correct location in memory to write their shellcode. They still have not...

      --
      Nature journal lied in Britannica vs Wikipedia Ask to retrac
    4. Re:Crash? I thought the original claim was... by CaymanIslandCarpedie · · Score: 5, Informative

      Not taking any sides here, but here is what he has said about this (and other issues) from his blog

      I thought you said it was a hijack yet you only showed a DoS.
      Yup, I showed a crash. I didn't feel the need to do the do the entire hijack for two reasons: Apple already confirmed that this vulnerability leads to remote code execution (they said so in the advisory here). Everybody that was running a sniffer during my talk now has a copy of the DoS code. The demo had two parts. I showed the crash happening on a 10.4.6 machine since it didn't have any of the airport patches. I then rebooted into 10.4.8 and the crash no longer happened. I did this to prove that the Airport patches issued on Sept 21st, 2006 fixed the problem I was demoing. The only real change to airport code was the security fixes that were issued.


      You just reversed the patches and found what you then showed on stage.
      I find this to be a funny argument. If I have the skills to reverse the patches and do a binary difference analysis of them, why couldn't I use those same skills to find the bugs in the first place (they weren't hard to find). This argument also doesn't take into account the fact that I showed that the first crash of the exploit occurred on Jul 15th, 2006, or emails to Apple helping them build a wifi auditing box (A linux machine with madwifi patched with LORCON) and pointed them to a vulnerability that was fixed in their patches (a problem with overly long SSIDs). The picture below is from the day I bought the Macbook, July 15th 2006. This crash occurred because I was fuzzing other devices and the Macbook crashed before I got to run the initial setup.

      --
      "reality has a well-known liberal bias" - Steven Colbert
    5. Re:Crash? I thought the original claim was... by Durandal64 · · Score: 3, Insightful

      This guy just doesn't quit. He claims that Apple confirmed that the vulnerability leads to remote code execution, which is bullshit. The description says "may be able to..." There's a world of difference there. Not every buffer overflow can be exploited to inject malicious code. It takes a lot of time and effort to actually find out whether it's practical to write an exploit, a lot more time and effort than simply patching the problem and being done with it. So why bother finding out for sure when you can just patch it and be sure that it won't get exploited?

      The fact that he will only demonstrate a crasher just seals the deal that he's full of shit. If he's had a working AirPort exploit for all this time, why not just demo it and put this issue to rest? That's what any sane person would do. But instead he's carefully misrepresenting Apple's release notes to make them seem as if they support his claim, further destroying his credibility.

      I think the most likely scenario here is that he originally found exploits for various third-party wireless drivers and saw an opportunity. With a cursory look at the AirPort drivers, he figured, "Yeah, I could write an exploit for them too". So he made a big announcement. He hated the "smug" Mac users, so now he could really stick it to them. But there was a problem. For whatever reason, he couldn't get his code to inject into the AirPort drivers. All he could do was KP the box. Well this wasn't what he initially promised. So when it came time to put-up or shut-up, he used a third-party card with drivers that he had been able to exploit. And of course, he knew that people would ask questions. Questions like, "Who cares? That card doesn't ship with Macs, and Macs have built-in wireless, so why would any Mac user ever need to buy this card?"

      Ah, but clever him. He knew that Apple had a reputation for being secretive and releasing the legal hounds. So he could just say, "Apple threatened me with legal action if I demoed the exploit on their drivers" and voila! He's now a victim of The Evil Corporation! The Slashdot crowd would definitely believe him. After all, geeks don't like Apple because they're secretive, and this would be just another validation for them. They'd buy it without question. Even if Apple issued a statement saying that Maynor was lying, that wouldn't matter, because Apple is the one who tried to muzzle Maynor in the first place! See how the logic goes round and round?

    6. Re:Crash? I thought the original claim was... by raynet · · Score: 2, Interesting

      Pretty solid video. I just want to add two things. First, the IEEE page says:

      Your attention is called to the fact that the firms and numbers listed may not always be obvious in product implementation. Some manufacturers subcontract component manufacture and others include registered firms' OUIs in their products.

      And second, though not sure about Macbooks and OSX, but often you can change your MAC address, though it would be silly to change it to Apple's OUI.

      So there is a small possibility that the video was real. Perhaps the shot where you see the Terminal.app was filmed at a later time, quite probable if they only used one camera for filming the demo.

      So, most likely a fake.

      --
      - Raynet --> .
  2. Just an observation..... by 8127972 · · Score: 2, Interesting

    Apple came out with a patch that addresses this issue:

    http://news.com.com/New+Apple+patch+plugs+Wi-Fi+hi jack+flaws/2100-1002_3-6118245.html

    The article doesn't mention if the machine he used in the demo had this patch. And if so, that may imply that the patch has holes.

    --
    This is my opinion. To make sure you don't steal it, it's covered by the DMCA.
    1. Re:Just an observation..... by donicer · · Score: 4, Informative

      There were two demos:
      One on 10.4.6 showing that it was vulnerable (crash achieved and remote code execution is possible).
      The second demo showed no crash on 10.4.8 showing that the patches Apple released did indeed fix the problem he pointed to.

  3. Proof in the pudding by Thrudheim · · Score: 4, Insightful

    I await the promised publishing of the email exchanges with Apple on his blog. If he shows that he actually did provide Apple with details on the exploit, then he might restore some credibility. As it stands, however, his demo yesterday sounds like more of the same obfuscation that has characterized this whole incident.

    1) In the original demo, he gained command-line access to the target machine (using a third-party wireless card). The claim was made to Brian Krebs in the Washington Post that the built-in wireless was similarly vulnerable (which would be far more relevant, since all MacBooks have built-in wireless). Yesterday's demo showed a crash of the target machine. That's bad, but he still has not demonstrated a takeover of the MacBook using the built-in wireless after all this time.

    2) The fact that Apple's patch addresses the flaw that caused the crashing does not prove that Maynor engaged in responsible disclosure. Apple has said that Maynor provided them with no code or other details about the exploit, and that they did their own investigation. The investigation, according to Apple, revealed a flaw, leading to the patch. The issue is NOT whether a flaw existed. All Maynor demonstrated was that Apple's security patch works, which is really not that enlightening.

    1. Re:Proof in the pudding by TPIRman · · Score: 5, Insightful

      This is the same bullshit please-connect-the-dots-for-me reasoning that Maynor has come up with all along. The question at issue is not whether there was a bug that allowed remote code execution. Yes, Apple has said as much. The question is whether Maynor had actually discovered such a bug. So far he has done nothing to dissuade objective observers that he's anything but an attention-grabbing fraud.

      Doesn't it strike you as the least bit shifty that Maynor, eager to clear his name and prove that he was right, suddenly doesn't "feel the need" to demo the hijack he originally claimed? Oh, but don't worry, he could hijack the MacBook if he really wanted to! According to Maynor, Apple has been lying and covering up through this whole ordeal, but now we are supposed to essentially take Apple's word for it that his crash demo = hijack. Please.

      Let's apply Occam's Razor here. Did Maynor fail to demo a hijack -- despite the fact that it would restore at least some his credibility -- because he thought it was just as convincing to piece together circumstantial evidence from Apple press releases? Or did he fail to demo a hijack because he can't? Are we supposed to believe that after all this time and humiliation, Maynor really doesn't "feel the need" to back up his inflammatory words? I don't buy it, and I don't see how any rational observer can.

      As the GP said, the proof is in the pudding -- all we've got here is a box that says "pudding mix, really!" and a promise from Maynor. Same as before. The guy is a charlatan.

    2. Re:Proof in the pudding by mjeffers · · Score: 3, Insightful

      Let's apply Occam's Razor here. Did Maynor fail to demo a hijack -- despite the fact that it would restore at least some his credibility -- because he thought it was just as convincing to piece together circumstantial evidence from Apple press releases? Or did he fail to demo a hijack because he can't? Are we supposed to believe that after all this time and humiliation, Maynor really doesn't "feel the need" to back up his inflammatory words? I don't buy it, and I don't see how any rational observer can.


      This is really the key point. To believe Maynor at this point you need to believe that someone who is concerned about repairing a tarnished reputation is so worried about people figuring out how he could exploit an already patched vulnerability that he decides to only show the crash rather than the take-over exploit. Maynor has a bone to pick with Apple/Apple users and managed to find a bug he couldn't find last year with the help of Apple's patch notes.

      If you need a security consultant to analyze your patch notes and find known vulnerabilities he's your man. Otherwise, he's a joke.
    3. Re:Proof in the pudding by Sancho · · Score: 2, Insightful

      You really have to piece together a lot of this puzzle to understand some of the underlying issues.

      Timing is everything with wireless. An overflow which causes a crash one time may allow for remote code execution the next. It's all very tricky to get right, and there are non-driver issues that can cause problems (things like interference, which you can't control). Maynor or Cache alluded to this at one point, and it was speculated that this might have been the real reason that they did a video demo instead of a live one--a live exploit demo which fails (but crashes the system) 6 times before it succeeds isn't all that impressive.

      So there were very similar (nearly identical) bugs in other vendor's drivers. FreeBSD had patched their version of the bug in January 2006. It was a similar exploit in a similar driver for similar hardware. It's far from a stretch to assume that he noticed his Macbook crash when he got it (he claims he was fuzzing other devices at the time here: http://erratasec.blogspot.com/2007/03/apple-infoan d-thats-all-folks.html ), he started investigating the chipset, found that it was Atheros, started researching the bug, and discovered the near identical one that had been patched 6 months ago. For someone with the knowledge, it should be trivial to adapt to the new platform, given the similarities between the FreeBSD and Apple drivers.

      Now it all gets pretty fuzzy around the time that they claim to be using 3rd party hardware. Why do that? Why does the video clearly show the Apple interface with an Apple MAC if they were using a 3rd party card?

      If we assume that he's lying, the video shows all of this because it was rigged. If we assume that he's telling the truth, then that is just more evidence to the "Apple coverup".

      The point of all of this, though, is that I think there's a certain amount of plausibility to all of this. I don't think that the situation I outlined above is a stretch. I do think that if it even remotely resembles the reality of the situation, then Maynor and Cache were exaggerating their own skills in determining the exploit. There was a pretty big inference by everyone at Blackhat that Maynor and Cache had discovered and engineered the exploit alone, not that it was based upon a pre-existing exploit for another OS. If they didn't intentionally imply that...well, then it sucks to be them, but their credibility takes a bit of a hit for it.

      Oh, and the timing issue I mentioned above? Could well be why he only demoed a crash instead of a full exploit this time. He's got Apple's word that remote code execution is possible, and he's shown that he can cause the crash. Who knows how many takes their video took to get right? With a live demo, you really only get one shot.

    4. Re:Proof in the pudding by Afecks · · Score: 2, Interesting

      You obviously know very little about exploits. If the bug allows remote code execution, which Apple plainly states is possible, the difference in a crash and a hijack is only a matter of a few bytes of shell code. So in essence he has done the hardest part already. Then you come along and claim that since he didn't take it all the way and give you the final easiest 1%, now he's a complete fraud and a liar.

      Even if he had demonstrated the original takeover that still wouldn't prove his story. Yet you claim that because of this it makes him look guilty. Nice logic. Basically, either way you get to claim he's full of shit.

      Many major vendors have a known history for screwing over vulnerability researchers such as Cisco, Apple, Microsoft and others. I just have a hard time believing this is any different.

    5. Re:Proof in the pudding by TPIRman · · Score: 4, Insightful

      If the bug allows remote code execution, which Apple plainly states is possible, the difference in a crash and a hijack is only a matter of a few bytes of shell code.

      You are buying into Maynor's fundamental misdirection here. He wants you to assume that the bug he is exploiting is the same as the bug that Apple says could allow remote code execution. But there is no evidence to support this assumption. Apple has fixed multiple AirPort bugs since 10.4.6. There is no way of knowing that Maynor is exploiting an AirPort bug that allowed a hijack rather than a crash.

      If it would only take "a few bytes of shell code" and the "easiest 1%" to make this exploit into a hijack, why not do it? His original claim was that he could hijack a MacBook, period. Now, supposedly given the chance to prove it, he just couldn't be bothered to slap together some shell code? Really? It's hard to believe that you don't find Maynor's "I can do that, I just don't feel like it" argument fishy at all.

    6. Re:Proof in the pudding by Afecks · · Score: 2, Funny

      It's hard to believe that you don't find Maynor's "I can do that, I just don't feel like it" argument fishy at all.

      What the hell are you talking about?! Whether or not he can do it is not the issue! Apple has admitted that it is possible.

      Here is TFA if you are too lazy to actually read it. Hell, since you like putting things in bold I'll help you out...

      Impact: Attackers on the wireless network may cause arbitrary code execution

      No no. That's not the bug Maynor was talking about, this is a different Wi-Fi remote code execution bug. Completely unrelated. Apple even pinky sweared.

    7. Re:Proof in the pudding by TPIRman · · Score: 4, Insightful

      Whether or not he can do it is not the issue!

      As I said above, that is, in fact, the issue. Nobody is disputing that a remote AirPort exploit was possible; that matter has been settled by Apple. You can be as sarcastic and triumphant as you want, but I already agree that there were documented remote-exploit bugs in Apple's code. Everybody does.

      The issue here is Maynor's reputation. A responsible security researcher has to be able to back up his claims. Maynor said he could hijack a MacBook. He never provided evidence that he could. Now he says, "Look, they fixed this AirPort bug, so I was telling the truth!" But he still doesn't demo the hijack, even on an unpatched machine.

      The debate over whether there were serious AirPort bugs has been settled. But Maynor has never demonstrated that he had the goods. He has left it to insinuation and sleight-of-hand. You have bought into his misdirection, and you still haven't answered the central question: If, as you claim, a remote takeover required only a bit of shell code, why not just do it?

      (Boldface added to that last bit purely out of love.)

  4. The reason he didn't actually show a takeover... by dpbsmith · · Score: 4, Funny

    Why didn't he simply show a repeat of the same thing he demonstrated before--a takeover of the machine?

    Because "a magician never repeats a trick."

  5. Re:apple can iFuck off by Space+cowboy · · Score: 4, Insightful

    So, let me get this straight

    1) he finds a bug, but he can't quite manage to exploit it. He can crash the machine (and that's a bad thing) but it doesn't *necessarily* mean he can exploit it.

    2) There's a big conference coming up, and he knows he'll get the headlines if he announces anything bad about Apple. That's just the way of the world. Dammit, he *still* can't find the exploit.

    3) The deadline arrives, he can't exploit the machine, but he goes ahead and gives the demo (faking the evidence with a different machine), confident that he'll get there eventually.

    4) He hides behind "legal issues" (even now, he won't reveal emails) to prevent himself from being exposed as the liar he appears to be.

    This series of events is just about the worst thing a researcher can do. It's like an athlete taking steroids - there will be no forgiveness, no olive-branch will be offered; his reputation is irredeemably tarnished, because he lied for personal gain. We *need* to be able to trust people publishing exploits, and if this means his career is in ruins, I say "Hurrah!" The less people like this around in the business, the better.

    I just want to also point out that I don't recall any lawyers being involved at any time in this dispute - neither party claimed lawyers were involved (he said Apple "leaned on" his employers, whatever that means, but lawyers were never mentioned.)

    Apple claim he released insufficient technical details to them to help them in their investigation, so they had to go to the trouble of doing a full internal audit of a large source tree (and all the time, he's spreading disinformation and tarnishing their name). They find and fix some bugs, and now he's in an even worse position - his crash "exploit" won't work.

    So, now, he releases the "details" - he's given up trying to exploit the original OS, and brushes that small point aside in the "details". He tries to save as much face as possible instead of admitting he was just plain wrong - he's basically covering his ass. Does anyone else think "details" ought to actually show the information he claimed to have (like being able to take control of a Mac in 60 seconds) ?

    In science, there are two fundamental maxims

          1) Don't falsify the data.
          2) Extraordinary claims require extraordinary evidence. (*)

    He failed, on both of these, as far as the world can tell.

    (*) "Extraordinary" here means in the technical sense - the first exploit of any kind requires unequivocal proof. I don't care if it's OSX, Windows XP, or Linux - show the data. Prove the case. Don't wave your hands around and babble.

    Simon.

    --
    Physicists get Hadrons!
  6. Re:The important point: by Rosyna · · Score: 3, Insightful

    Apple admitted the vulnerability WAS a root exploit.

    No, Apple said it could be used to run arbitrary code with system privileges.

    Just like I could step outside my door and find $10,000 rolled up in a neat little ball. Doesn't mean it is likely to happen, but it could.

    Theory and practice are two completely different things.

  7. Re:The important point: by MasterVidBoi · · Score: 2, Insightful

    It was a WiFi-borne hack and he was at Black Hat. So there were lots of sniffers going and everybody gets a copy of whatever he does.

    So he just demoed (and thus released) the DoS, not the root exploit - which he DID have the code to perform but didn't want to release (by demoing). Except that the patch for this vunerability was released months ago. Yet that didn't stop him from (trying) to do the demo at Black Hat 2006, when there would have been just as many sniffers in the audience.

    From someone who already threw out their credibility, that really doesn't inspire confidence.
  8. Re:The important point: by Sancho · · Score: 2, Informative

    I was at that Black Hat talk in Vegas. They didn't do the demo--they showed a video of it. They did it this way PRECISELY because there were sniffers in the audience.

  9. Re:apple can iFuck off by Fahrenheit+450 · · Score: 4, Insightful

    No. That is a link to a story with a great lack of details and a number of still unsubstantiated claims.
    There is still no public supporting evidence for his clams -- he hasn't even posted his personal correspondence with Apple yet, something he'd been free to do since day one.

    Maybe he'll get around to it someday... who knows. But for now it's still just a lot of words with no support.

    --
    -30-
  10. Re:The important point: by veganboyjosh · · Score: 5, Funny

    Theory and practice are two completely different things.


    not in theory.

  11. Re:apple can iFuck off by Fahrenheit+450 · · Score: 2, Insightful

    It really kills you that somebody who saw his presentation now believes him doesn't it.

    Not at all. Though it does bother me that someone is willing to call something truth when there is still no evidence made public to substantiate it.

    And regardless of how reputable The Register is, the article provides no information that support the reporter's conclusions. And until Maynor publishes those emails, there won't be any. He's already posted two updates to the blog since his presentation, including one that pertains to why he can't release his old work emails, but he hasn't yet made the personal ones available (nor has he even claimed that his old company won't allow him to release the old emails, just that they aren't his property and that releasing them without permission could be bad -- has he even asked for permission?).

    Cases like this call for as much disclosure as is possible, and he hasn't come close to that yet. It's still a bunch of "oh, I plan to do this" and "oh, I could do that" with no backup. Either provide all of the info that you can, or shut up. That's all that's been asked since day one.

    --
    -30-
  12. Re:Yes it does! by Space+cowboy · · Score: 3, Insightful

    When it's due to memory corruption and when you can overwrite certain registers, it DOES mean that arbitrary code execution is possible. It may be pretty damn difficult to get just the right values in there, but this is one case where you can be 99.999% certain that it really is exploitable.

    If you don't believe me, please give a non-contrived example where you can do something like overwrite the EIP with an arbitrary value and still not be able to execute arbitrary code :P


    I refer the honourable gentleman to the reply I gave some moments ago - if he can do it, he ought to do it. Until he does it, I don't believe he can do it.

    So, here's your example: the exact "exploit" he's claiming to be able to perform.

    Lastly, the "extraordinary" in "extraordinary evidence" is a purely subjective matter


    No, it's not. Which is why I used "in the technical sense" in the original comment. "Extraordinary" means "out-of-the-ordinary" - the claim is not run-of-the-mill, it's the first remote exploit of an Apple laptop. The proof should also be bulletproof (actually, right now I'd settle for just proof, not incontrovertible evidence!) At the moment, all we have is a load of hot air and bluster.

    Simon.
    --
    Physicists get Hadrons!
  13. Mistakes? by dr.badass · · Score: 2, Insightful

    I'm still waiting for a demo of this phantom exploit on a Windows machine:

    "Maynor said the two have found at least two similar flaws in device drivers for wireless cards either designed for or embedded in machines running the Windows OS. Still, the presenters said they ultimately decided to run the demo against a Mac due to what Maynor called the "Mac user base aura of smugness on security."

    "We're not picking specifically on Macs here, but if you watch those 'Get a Mac' commercials enough, it eventually makes you want to stab one of those users in the eye with a lit cigarette or something," Maynor said." -- Hijacking a Macbook in 60 Seconds or Less

    Actually, what I'm really waiting for is for Maynor to stop opening his mouth.

    --
    Don't become a regular here -- you will become retarded.