Vulnerabilities in Heroku's Build System

http://titanous.com/posts/vulnerabilities-in-heroku-build-system

by Titanous • 14 years ago

170 34 14 years ago

illamint• 14 years ago

Perhaps a fantastic example of why keeping detailed configuration in environment variables is probably a bad idea. Your private SSH key isn't part of the environment. It's configuration. Treat it as such.

bigiain5• 14 years ago

Not sure that would have helped much in this case - he used dumping the environment as the particular avenue to get the "private" data, but he mentioned he had source code access and the ability to run untrusted code. If important credentials were in or available to the code, it sounds like they would have been vulnerable anyway.

It's a hard problem trying to secure credential that code needs to work, from other code running as the same user when someone has source code access to "authorised" code.

seany• 14 years ago

Thank you for taking the high road and exposing the issue rather than giving them the option to hide it (not saying they would).

cjeane• 14 years ago

This is the concept of Full Disclosure. http://en.wikipedia.org/wiki/Full_disclosure

kposehn• 14 years ago

Very glad to see this not only documented, but patched extremely quickly. Heroku continues to impress, and Titanous is a credit to the security profession.

redslazer• 14 years ago

This is a really interesting insight into the way someone found access to a system but could someone explain to me why he needed PGP keys from heroku? I'm sure there is some good reason but if someone could tell me that would be great.

leftnode• 14 years ago

It's standard practice to encrypt your emails when sending potential security notifications to the party that you're notifying. Not only does it keep out prying eyes, it ensures the person sending the email is who they say they are.

bigiain5• 14 years ago

"it ensures the person sending the email is who they say they are"

Although, if you're going to trust the pgp key you get sent when you mail someone asking for one, you don't have any more assurance that you're encrypting it to the person you intended, and you _almost_ may as well have sent it in cleartext in the initial email...

Get your pgp fingerprints in some out-of-band method of communication. (When was the last time anybody even heard of a key signing party? I attended on at the Perl Conference in '98 or '99 - don't think I've been aware of one happening in any of my circles since)

lawn• 14 years ago

That's a nice way of handling it, both from heroku and you who found the exploit. I feel content with my choice to use heroku.

justincormack• 14 years ago

Well someone could have easily discovered the environment variables vuln without getting the source code, although it is unclear why so much was disclosed in env vars. It suggests that everything runs as the same user, or you would not get anything.

tptacek4• 14 years ago

Heroku offered me a paid penetration test contract, but required that I sign a retroactive non-disclosure agreement which would have precluded publishing this article.

Worth pointing out: virtually all paid pentesting engagements are delivered under NDA. In fact, more often than not, they're done under the far-stricter terms of a master agreement with detailed IP clauses.

If you're talking to any firm about having your app tested, get an NDA in place, and don't feel bad about asking. Nobody who thinks they need it should forestall having their app checked out because they think the firm they're going to work with is going to try to make news out of their findings.

Obviously, if your customers find vulnerabilities themselves, all bets are off!

Titanous3• 14 years ago

Of course there was never any question that any new penetration testing I would do with them would be under NDA. What worried me is that the disclosure may not be made public if I was under a NDA that prevented me from publishing it. I didn't want to have any professional or ethical conflicts.

tptacek4• 14 years ago

You were right: once you had engaged a unit of Salesforce for an app test, it would have been extremely difficult for you to publish this. Not black-letter impossible, but difficult.

novalis• 14 years ago

The retroactive part of the deal was a clear ominous alarm and you acted accordingly. I find great joy in knowing that you showed a pristine level of ethic behaviour in your security research. Well done.

david_shaw• 14 years ago

I can't blame Titanous under these circumstances, though.

It's a whole different ballgame when you're testing applications under contract (as I know you know), but as a budding researcher/security guy, it might be better for him to publish via responsible disclosure (as he did just now) than to accept a temporary (presumably secret) contract.

I know that ethical disclosure is a whole can of worms that isn't completely relevant to this conversation, but I'm a firm believer that Titanous went about this the right way. First off, he is the customer (as a Heroku user), and secondly he notified Heroku and waited until the vulnerability was fixed before publishing his findings. If all researchers behaved in such a responsible way, we'd probably be in a better place as an industry.

Anyway, the point I'm making is that, sure, having a penetration testing contract with Heroku might have been nice for his career, but I think being able to point to this research that he's conducted on his own and responsibly disclosed is far better. Hell, I'd offer him a job right now if he seemed interested.

tptacek4• 14 years ago

I hope it doesn't sound like I'm blaming him for anything. I'm not.

AndyKelley• 14 years ago

I'm happy to see both parties in this situation acting with a great deal of professionalism. It feels good to be a part of this community.

Titanous3• 14 years ago

Heroku's official response: http://blog.heroku.com/archives/2012/7/3/codon_security_issu...

danso• 14 years ago

This is a minor point, but one of my favorite details: the use of a simple table for the "Disclosure Timeline", which is really the clearest way to illustrate the step-by-step sequence of events. I would love to see this be a standard practice for any narrative in which order/visual comparison is vital. HTML tables are so easy to include (or, even bulleted lists).

A masterful explanation, on top of being an altruistic deed.

sodelate• 14 years ago

the page is well composed

Vulnerabilities in Heroku's Build System

Related Stories