News for hackers. Stuff that matters.
Re:Security researcher Charlie Miller booted from Apple Deve... by Xuzz on Monday November 07, 2011 @09:34PM (#3209248)
I'd agree more if he didn't submit — and get approved — a working exploit in their store. Without telling them about it.

Edit: Now, I don't disagree that just banning him from the program isn't a great idea, and that pulling the app and having someone from the security team send him an email isn't a better one. But it's hard to say this that a bad move on Apple's part.

Re:Security researcher Charlie Miller booted from Apple Deve... by jjguy on Tuesday November 08, 2011 @07:47AM (#3210503)
From Miller's twitter stream last night:

For the record, without a real app in the AppStore, people would say Apple wouldn't approve an app that took advantage of this flaw.

https://twitter.com/#!/0xcharlie/status/133739410662494208

Re:Security researcher Charlie Miller booted from Apple Deve... by nodata on Tuesday November 08, 2011 @01:44AM (#3209770)
So how do you prove that it's possible to get this kind of exploit into the store unless you submit it to the store?
Re:Security researcher Charlie Miller booted from Apple Deve... by ubernostrum on Tuesday November 08, 2011 @02:04AM (#3209810)
So how do you prove the DDoS vector exists unless you DDoS someone's site?

How do you prove the SQL injection vector exists unless you take over someone's site?

etc., etc.

This was far from a harmless proof-of-concept app, and "I just wanted to prove I could" isn't sufficient justification for it.

Re:Security researcher Charlie Miller booted from Apple Deve... by redthrowaway on Tuesday November 08, 2011 @02:21AM (#3209838)
You prove DDoS vectors exist by DDoSing your own site, or one you have permission to work on. Same with SQLi vulnerabilities. If you want to report a vulnerability you've found to a company, include a working exploit in your report, but don't run it. If the company ignores you or tries to brush the vulnerability off, that's where it gets hairy and responsible disclosure comes into play.

We don't know what his level of communication was with Apple, but it doesn't appear that he notified them before testing this exploit. Had they refused to address the issue or otherwise brushed him off, this would be a reasonable escalation. The same story on r/netsec [1] is being linked to a Forbes article [2], which claims he notified Apple three weeks ago. That's not a ton of time.

Ultimately, he very much violated their ToS and Apple is well within their rights to give him the boot. Whether that was a smart decision on their part remains to be seen.

[1] http://www.reddit.com/r/netsec/comments/m48gx/charlie_miller... , http://www.reddit.com/r/netsec/comments/m3uwo/mac_hacker_cha...

[2] http://www.forbes.com/sites/andygreenberg/2011/11/07/apple-e...

Re:Security researcher Charlie Miller booted from Apple Deve... by doron on Tuesday November 08, 2011 @10:03AM (#3210960)
Since the only place you can install software on iOS devices is through the store, it is important to demonstrate the attack vector by which it can be gained.

It indicates both a security flaw in the platform itself, and a security flaw in the app store approval process, both should be highlighted.

Re:Security researcher Charlie Miller booted from Apple Deve... by joelhaasnoot on Tuesday November 08, 2011 @07:58AM (#3210531)
Since he has control over pricing, couldn't he submit with a free price tag, and change it to something insanely high once accepted. That way no sane person would buy it, and he'd still prove his point. He _had_ to submit an app and get it in for this to work ofcourse, otherwise this was a moot point. And it's a good wakeup call to everyone. Security awewareness helps sometimes unfortunately when you make a splash.
Re:Security researcher Charlie Miller booted from Apple Deve... by alttag on Tuesday November 08, 2011 @08:19AM (#3210589)

  > .. otherwise this was a mute point.
"moot". Pretty please, the word is "moot."

Otherwise, while I think you've got a point (he could have used pricing to ensure no one ran his app), that isn't the issue here. The disclosure is. No one is contending he did something evil with his code, it's that Apple is mad about his code and disclosure. I don't think making it unlikely to be purchased would have helped.

Re:Security researcher Charlie Miller booted from Apple Deve... by rmc on Tuesday November 08, 2011 @04:36AM (#3210091)
You don't need to "take over someone's site" to prove that their site has a SQLI vector, just put in a little string somewhere.
Re:Security researcher Charlie Miller booted from Apple Deve... by mike-cardwell on Tuesday November 08, 2011 @06:01AM (#3210271)
In the UK, using SQL injection to "put a little string somewhere" would be illegal.
Re:Security researcher Charlie Miller booted from Apple Deve... by rmc on Tuesday November 08, 2011 @07:16AM (#3210423)
Oh probably. But I'm pointing out that you can demonstrate a SQLI attack without having to completly take down someone's site.
Re:Security researcher Charlie Miller booted from Apple Deve... by guelo on Tuesday November 08, 2011 @05:29AM (#3210200)
Those things have already been proven. We're talking about research here.
Re:Security researcher Charlie Miller booted from Apple Deve... by Xuzz on Tuesday November 08, 2011 @02:13AM (#3209827)
For one, he could have submitted it and then have it "held for developer release" — at which point he told them about it. There's no reason he had to have it actually in the App Store here, even if he wanted to test the approval process.
Re:Security researcher Charlie Miller booted from Apple Deve... by Confusion on Tuesday November 08, 2011 @01:58AM (#3209797)
^^This. And he [1] probably told them immediately afterwards, since otherwise they still wouldn't have known. As he says: he regularly submits bugs.

[1] Or perhaps someone beat him to it: he may not have seen the acceptance mail before someone already noticed the app? I'm not familiar with the exact process: do you need to give final approval or can the app be in the store for a while without you knowing it?

Re:Security researcher Charlie Miller booted from Apple Deve... by 16s on Tuesday November 08, 2011 @07:36AM (#3210474)
Perhaps he's not the first one to do it? Only the first to tell Apple that he did it.
Re:Security researcher Charlie Miller booted from Apple Deve... by mikeash on Monday November 07, 2011 @10:45PM (#3209424)
This hardly qualifies as an exploit. While it allows the app to do something it's not supposed to do, the ability to download and execute additional executable code doesn't actually violate security. The new code is still restricted to the app's sandbox and can't do anything that the original app couldn't potentially have done directly.
Re:Security researcher Charlie Miller booted from Apple Deve... by humbledrone on Monday November 07, 2011 @11:27PM (#3209506)
It easily qualifies as an exploit, given that Apple's app store model is based on the fact that each app is reviewed beforehand to ensure various properties, including the property that the app does not contain spyware, etc. If Apple approved a harmless app, and then said app downloaded code that snooped on the user's calls or asked for their credit card number, that's an exploit.
Re:Security researcher Charlie Miller booted from Apple Deve... by ghshephard on Tuesday November 08, 2011 @12:37AM (#3209645)
First - I think just general manners, as well as established protocol, would have the security researcher let Apple know ahead of time what he would be doing. A simple email sent prior to uploading this code would have been sufficient to cover his bases - I'm surprised he didn't do that.

Second - Unless I'm mistaken - his proof of concept was more a violation of Apples TOU, it didn't really attempt to copy credit card numbers, or snoop on users calls - so, in that sense, it wasn't an exploit.

Net-Net - nobody comes out of this looking good, but Apple makes it clear that they are prepared to back up the language of their Developer TOU with actions.

Re:Security researcher Charlie Miller booted from Apple Deve... by JoachimSchipper on Tuesday November 08, 2011 @01:04AM (#3209694)
Part of the security of the app store is the review process. "It's possible to download and execute code" is neat, "it's possible to download and execute code and the app store reviewers don't catch that" is much more impressive.
Re:Security researcher Charlie Miller booted from Apple Deve... by ghshephard on Tuesday November 08, 2011 @02:21AM (#3209837)
Nothing in the App Store review process will allow them to catch a zero-day exploit. Coming up with a zero-day exploit in IOS is very impressive - but, by definition, once you have it, the App Store review process isn't going to catch it.
Re:Security researcher Charlie Miller booted from Apple Deve... by mikeash on Tuesday November 08, 2011 @08:10AM (#3210567)
App review ensures no such thing. Put in your spyware with a timer so it doesnt activate for a week. Boom, reviewers don't see it, and users do.
Re:Security researcher Charlie Miller booted from Apple Deve... by freemarketteddy on Tuesday November 08, 2011 @10:54PM (#3214178)
lol...timer!!....really?
Re:Security researcher Charlie Miller booted from Apple Deve... by mikeash on Wednesday November 09, 2011 @10:50AM (#3215940)
Yep. There's no deep check of what your code contains, only a fairly superficial check of what it actually does. You can include nearly anything in your app (perhaps lightly obfuscated) as long as it doesn't show its face during the review.
Re:Security researcher Charlie Miller booted from Apple Deve... by freemarketteddy on Wednesday November 09, 2011 @11:00AM (#3215977)
yes that is indeed true...but why a timer?....you can just query your own web server and figure out what to do.

But yeah if you dont have time to make a small web server the timer idea could also work.

Re:Security researcher Charlie Miller booted from Apple Deve... by mikeash on Wednesday November 09, 2011 @11:15AM (#3216052)
Depends on your level of paranoia and willingness to rely on the network. The server has the advantage of letting you turn it on and off at will, but a timer will work even if the user has no internet connection or your server gets confiscated by the FBI.
Re:Security researcher Charlie Miller booted from Apple Deve... by st3fan on Tuesday November 08, 2011 @05:52AM (#3210249)
I think it qualifies as a great exploit. You totally go around the Private API checks that Apple does. And there is a lot you can do with those APIs that is potentially evil. Even in the sandbox.
Re:Security researcher Charlie Miller booted from Apple Deve... by mikeash on Tuesday November 08, 2011 @08:06AM (#3210555)
It's trivial to bypass those checks anyway.
Re:Security researcher Charlie Miller booted from Apple Deve... by nookiemonster on Tuesday November 08, 2011 @04:10AM (#3210019)
Running unsigned code is an exploit, my friend.
Re:Security researcher Charlie Miller booted from Apple Deve... by mikeash on Tuesday November 08, 2011 @08:23AM (#3210605)
Why? What can you accomplish by running unsigned code that you can't accomplish by embedding a (e.g.) Python interpreter?
Re:Security researcher Charlie Miller booted from Apple Deve... by nookiemonster on Tuesday November 08, 2011 @11:24AM (#3211335)
Code signining is a control that is intended to restrict the software that can run to only those apps which have been granted the right to run.

Your second question is a good one, but given is context, it is unrelated. If apple signs a python interpreter, they do so at their peril, for obvious reasons.

Re:Security researcher Charlie Miller booted from Apple Deve... by mikeash on Tuesday November 08, 2011 @11:41AM (#3211427)
Yes, and it's still only running an app which was granted the right to run, it's just that this app now has some extra code in it. Since Apple doesn't really inspect the contents of the apps it signs anyway, this grants no extra capabilities.