News for hackers. Stuff that matters.
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by mocko on Tuesday January 08, 2013 @08:58AM (#5026166)
This is an example of how a competent cracker (as opposed to a script kiddie) works. He's:

1) Identified a badly protected side entrance to use rather than the front door

2) Painstakingly researched the third party product (similarly one could investigate a third party library used in a bespoke codebase)

3) Figured out the adaptations the target organisation had made to it and guessed some mistakes they'd made

4) Eventually hit on a cookie modification attack made possible by limitations found in that publicly-available codebase.

Smart.

Re:How I Hacked Facebook’s Secure Files Transfer Service for... by MojoJolo on Tuesday January 08, 2013 @09:15AM (#5026248)
Let's also add the fact that he reported it so that it can be fixed immediately. :)
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by tripzilch on Tuesday January 08, 2013 @12:35PM (#5027249)
While certainly commendable, it does not make the difference between a script kiddie and a competent cracker :)
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by MichaelGG on Tuesday January 08, 2013 @11:38AM (#5026967)
"This Version of ionCube was not vulnerable to a possible decryption"

Does he just mean "this version doesn't have a readily available dissassembler yet"? Even if they chose the path of compiling to native code, if you own the box, it can't be that hard to get the code.

Re:How I Hacked Facebook’s Secure Files Transfer Service for... by maqr on Tuesday January 08, 2013 @12:27PM (#5027201)
I wish he'd gone down this route further. It looks like there's code at the top of the file that "decrypts" (decodes?) the contents of the PHP file. I'd be curious why he felt this wasn't worth reversing.

I'm also curious if there's a way to dump 'disassembled' PHP after it's been loaded into the PHP processor. If it's going through eval() at the end, then shouldn't the plain-text source be available in a string somewhere?

Re:How I Hacked Facebook’s Secure Files Transfer Service for... by 0x0 on Tuesday January 08, 2013 @12:39PM (#5027274)
I believe these obfuscators work by forcing you to install a binary-only .so zend extension in php.ini, which intercepts these encoded files. The files themselves should decode to already-halfway-parsed PHP opcodes or so, which is probably injected into the PHP/Zend virtual machine.

Figuring out the encoding scheme is probably a lot of boring disassembly work, which in the end just lets you decode a bunch of PHP opcodes which themselves would take a lot of work to make sense of.

But perhaps the Vulcan Logic Dumper could help out a little bit. http://derickrethans.nl/projects.html#vld

Re:How I Hacked Facebook’s Secure Files Transfer Service for... by elbear on Tuesday January 08, 2013 @02:51PM (#5028064)
Yes, there is. I've used a PHP extension called evalhook for that.
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by Dylan16807 on Tuesday January 08, 2013 @10:06AM (#5026472)
I like this but what the hell is the problem with base64?

'Still alive these day?'?

It's useful for what it does, always has been, never been a security feature.

Re:How I Hacked Facebook’s Secure Files Transfer Service for... by darkarmani on Tuesday January 08, 2013 @10:24AM (#5026572)
He was paraphrasing: "i didn't think base64 (for encryption) was still alive these days?"

People unfortunately have used it as a security feature in the past.

Re:How I Hacked Facebook’s Secure Files Transfer Service for... by CountHackulus on Tuesday January 08, 2013 @10:15AM (#5026521)
The problem is that they're using it for encryption.
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by Nitramp on Tuesday January 08, 2013 @10:32AM (#5026631)
They are using it to make sure the value doesn't interfere with the syntax of HTTP headers, i.e. for escaping, not for encryption. That's exactly what base64 is for. They simply have no encryption at all.
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by rplnt on Tuesday January 08, 2013 @11:18AM (#5026885)
Can email interfere with HTTP headers though? There's no \r\n, ";" or "=" in valid email.

Anyway, I have seen sites where it was used as a security measure. Or so the authors thought I guess. Storing login password in url parameter? Seems safe if it is encoded.. But it was years ago.

Re:How I Hacked Facebook’s Secure Files Transfer Service for... by hoov on Tuesday January 08, 2013 @11:43AM (#5026993)
Actually, the '=' character is allowed. [1]

[1] http://tools.ietf.org/html/rfc5322#section-3.2.3

Re:How I Hacked Facebook’s Secure Files Transfer Service for... by ddunkin on Tuesday January 08, 2013 @12:49PM (#5027317)
It sounds like you confused encoded with encrypted, encoded is no different than plain-text. The encoding is just to get a valid string for the URI (so a password can contain special URI characters) and is instantly reversible.
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by rplnt on Wednesday January 09, 2013 @03:56AM (#5030769)
No, I haven't. Should have put the "security measure" in the quotes.
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by papsosouid on Tuesday January 08, 2013 @02:33PM (#5027973)
>There's no \r\n, ";" or "=" in valid email.

Both ; and = are perfectly valid.

Re:How I Hacked Facebook’s Secure Files Transfer Service for... by rplnt on Wednesday January 09, 2013 @04:00AM (#5030779)
Did not know that, thanks for pointing that out. In that case the encoding is necessary. On top of that I just found out that even Unicode characters are permitted (RFC 6531).
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by weej on Tuesday January 08, 2013 @01:28PM (#5027562)
Exactly. Initially, I was confused by this statement too.

There's nothing wrong w/ base64 encoding; however, one needs to apply it to the correct context like applying it to: hashes, avoid text collision/escaping chars, or just embedding plain old non-sensitive binary data in text.

Re:How I Hacked Facebook’s Secure Files Transfer Service for... by Sami_Lehtinen on Tuesday January 08, 2013 @02:09PM (#5027807)
This is also used as encyption in many projects. It's incredible and crazy stuff. http://www.codango.com/asp/fnc/review-hot/?id=2303410

It's very easy to Google and see tons of sites using it. Many sites using it got serous security flaws.

Re:How I Hacked Facebook’s Secure Files Transfer Service for... by dmak on Tuesday January 08, 2013 @11:07AM (#5026818)
Why does an enterprise level SaaS have such weak security? It is a rookie mistake for a company who emphasizes security.
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by fleitz on Tuesday January 08, 2013 @09:05PM (#5029708)
I don't think you've worked with many 'enterprise' level software products. Enterprise basically means has a salesforce willing to slog through an RFP.
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by ing33k on Tuesday January 08, 2013 @10:17AM (#5026529)
I understand that facebook has other important things to do ,than create their own file sharing service( for internal purpose ), but I can't stop asking this question, why not create their own thing ?
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by 0x0 on Tuesday January 08, 2013 @10:22AM (#5026556)
Well you pretty much answered your own question, didn't you?

Surely it is cheaper to buy an off-the-shelf solution, instead of spending a lot of money on wasting engineering time building and supporting a product that is not core to their mission.

Re:How I Hacked Facebook’s Secure Files Transfer Service for... by xxpor on Tuesday January 08, 2013 @10:52AM (#5026742)
It's DRY, applied over the entire industry.
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by cool-RR on Tuesday January 08, 2013 @09:29AM (#5026319)
I'm confused. This looks like an interesting hack, but I don't understand what's going on here, despite reading the post 4 times and watching the video twice.

What is this "Password Recovery" page? Is this for emailing a person a reset link to a password? Is it for changing your password? What is the cookie used for? What is the flawed logic in the system?

Can anyone explain this more clearly please?

Re:How I Hacked Facebook’s Secure Files Transfer Service for... by benmanns on Tuesday January 08, 2013 @09:44AM (#5026393)
I think the process was that a user was sent a 'forgot password' link. When they clicked the link, they were redirected to `wmPassupdate.html` with the cookie `referer={base64(email)}` set. Then, when users submit the password update form, the `referer` cookie is used to authenticate them, but it can be trivially generated.
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by recuter on Tuesday January 08, 2013 @10:10AM (#5026490)
tptacek will be shortly along to explain how password reset links are typical and one of the most common mistakes.

How you should just "take the hit" (the cost is trivial) and store a randomly generated nounce in your database rather then do shenanigans like encoding user information in the url with secrets and bad cryptography and what not.

See? We listen! :)

Re:How I Hacked Facebook’s Secure Files Transfer Service for... by lbotos on Tuesday January 08, 2013 @10:30AM (#5026617)
Do you have any examples of someone further explaining what you are suggesting? Or if you have time, can you further elaborate on this point? I glanced at the nounce article on wikipedia and if I understand correctly you are suggesting:

1) user creates account (which generates nounce)

2) when password resetting via email auth via nounce.

3) when password is reset regen nounce

Is that right? Just trying to better understand what appears to be a good approach to password resets.

Re:How I Hacked Facebook’s Secure Files Transfer Service for... by recuter on Tuesday January 08, 2013 @11:08AM (#5026822)
Here's a recent post of somebody else channeling tptacek: http://news.ycombinator.com/item?id=4940291

I got it from a quick 'password reset' search here, I recall a lot of these discussions, if you're curios click around on a few more results. :)

Re:How I Hacked Facebook’s Secure Files Transfer Service for... by ahlatimer on Tuesday January 08, 2013 @11:10AM (#5026838)
That's basically right. Generally you generate the nonce when someone clicks the 'forgot password' link, but I suppose you could do it when someone creates the account as well.
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by pyre on Tuesday January 08, 2013 @10:44AM (#5026704)
I'm confused. How exactly is the nonce to be used if without a link?

I was under the impression that best practice was a link with a randomly generated key that has an expiration date (and is expired as soon as it is used). The only security hole here is if the email is intercepted (and you've got other problems at that point).

Re:How I Hacked Facebook’s Secure Files Transfer Service for... by superuser2 on Tuesday January 08, 2013 @10:56AM (#5026762)
This system didn't use a nonce or a key referenced against a database. It simply base-64 encoded the email address.
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by andrewcooke on Tuesday January 08, 2013 @07:44PM (#5029440)
i think you're actually agreeing. what one of you is calling a key the other calls a no[u]nce.

the implicit (worse) alternative is that you encrypt or sign additional state in the url (and in this case, base64 was the "encryption").

Re:How I Hacked Facebook’s Secure Files Transfer Service for... by pyre on Wednesday January 09, 2013 @12:49AM (#5030386)
I realize that key == nonce in my post. My point was against the statement "emailing password reset links is bad and not best practice." You need an password link to make use of the key/nonce. The point of the nonce isn't to eliminate links. It's to make the attack surface that much smaller by limiting their power.
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by kalleboo on Tuesday January 08, 2013 @09:45AM (#5026404)
It sounds like the link in the "Password reset" email doesn't use a secret one-time expiring token, but instead base64-encodes the user's email address, so it can trivially be generated by an attacker.
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by darkarmani on Tuesday January 08, 2013 @10:28AM (#5026605)
Not just that, but there was a self-help page for self-registering your own account (the first screenshot):

> It seems that Facebook was trying to avoid the creation of accounts in Accellion after removing the register form from the pageview

> I discovered that if you know the direct location of the form (/courier/web/1000@/wmReg.html), You can easily bypass that protection and create an account in files.fb.com,

Once he created his own accounts, he could test out his exploit code on his created accounts.

Re:How I Hacked Facebook’s Secure Files Transfer Service for... by denysonique on Wednesday January 09, 2013 @06:55AM (#5031125)
Here is another Facebook vulnerability, a more serious one -- a password reset bug: http://chingshiong.blogspot.in/2013/01/facebook-bug-4-passwo...
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by secure on Tuesday January 08, 2013 @09:01AM (#5026182)
For a non-facebook user/employee, can someone please explain which service that is?
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by davidradcliffe on Tuesday January 08, 2013 @09:07AM (#5026210)
Internal company file sharing.
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by duck on Tuesday January 08, 2013 @09:20AM (#5026270)
Not just internal, but external as well. Instead of emailing a large file to a vendor, you would send them a link.
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by davidradcliffe on Tuesday January 08, 2013 @09:26AM (#5026300)
Oh true!
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by bmohlenhoff on Tuesday January 08, 2013 @08:58AM (#5026165)
The date in the last screenshot (19/3/2012) doesn't match the date in the rest of the images (7/1/2013).
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by bradleyland on Tuesday January 08, 2013 @09:35AM (#5026347)
The last screenshot is a capture of Windows Media Player playing back a desktop video capture session; basically screenshot inception. The author provides no information on timelines, so it's likely that he found this exploit back in March of 2012, but is just releasing the write-up now.
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by dmak on Tuesday January 08, 2013 @11:05AM (#5026810)
I think he made a whitehat report and probably waited for everything to be fixed before releasing a write up.
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by bcl on Tuesday January 08, 2013 @08:40AM (#5026111)
Depending on user supplied data for password changes? Not a good idea...
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by dreamdu5t on Wednesday January 09, 2013 @02:18AM (#5030579)
Soon i will publish OAuth bypass in Facebook.com, Cya Next time!

hrm?

Re:How I Hacked Facebook’s Secure Files Transfer Service for... by el_duderino on Tuesday January 08, 2013 @04:55PM (#5028761)
Windows Media Player?

O_o

Re:How I Hacked Facebook’s Secure Files Transfer Service for... by kingdm on Tuesday January 08, 2013 @09:04PM (#5029706)
What's wrong with WMP? :)