News for hackers. Stuff that matters.
Re:Browser Vulnerability to Superfish: A Fact-Finding Trip t... by patcheudor on Thursday February 19, 2015 @09:21PM (#9078536)
I went to Best Buy as well today and picked up a laptop to look into this further. The Superfish software is not properly passing the validation state of the public cert when it connects to a website like Bank of America as an example. There's no need to export their private and use it in a MitM transparent proxy. The software is simply not triggering appropriate warnings when provided an obviously fake certificate that has been generated in a way to bypass browser warnings. It's also not properly validating revoked certs. Both of these situations are very bad. Allowing any self-signed cert would lead me to believe that this could have easily been exploited in the wild without prior knowledge of this vulnerability.

I'm not going to provide a how-to guide on how to exploit users here. I have notified both Superfish and Lenovo of this issue and here's an example of the improper status pass through based on doing something that might be quite obvious to some:

This is what the browser should do when it encounters a self-signed cert delivered by an SSL/TLS MitM solution:

http://defaultstore.com/six.png

However, it's not doing this for this self-signed public cert:

http://defaultstore.com/four.png

Note both certs show "verify_fail." at the beginning and those who know how browser cryptography works will understand what has gone wrong with their implementation.

Re:Browser Vulnerability to Superfish: A Fact-Finding Trip t... by userbinator on Thursday February 19, 2015 @09:41PM (#9078599)
I suppose they were relying on the prepending of "verify_fail" to the hostname (with an invalid character - '_') to cause the browser to fail the certificate name check, so Superfish is doing certificate checking? Shouldn't the browser then complain with a "certificate's hostname does not match the site's" warning?

...Or am I looking at this in the wrong way?

Re:Browser Vulnerability to Superfish: A Fact-Finding Trip t... by patcheudor on Thursday February 19, 2015 @09:46PM (#9078616)
You're close. I'm not in the business of telling people how to exploit this and am assuming those who already know were already doing it based on what would be a "best practice" (for a bad guy that is) when it comes to generating a self-signed cert.
Re:Browser Vulnerability to Superfish: A Fact-Finding Trip t... by ryan-c on Thursday February 19, 2015 @10:34PM (#9078763)
...is it blindly copying any x509v3 attributes present on the certificate, or just the one that you seem to be carefully not mentioning? Can you email me (one is listed in my HN profile)? I just thought of a pretty horrible exploit. 2199399413f2e63e6291a3f3e60f3475518aaf88215434222c65d6bc6fe41f34
Re:Browser Vulnerability to Superfish: A Fact-Finding Trip t... by userbinator on Thursday February 19, 2015 @11:00PM (#9078837)
After a little more thought, it seems obvious to me now what the problem is. :-)

The shocking thing is that the certificate name matching algorithm has been standardised for over 15 years and yet those who wrote the cert generation code weren't aware of how browsers implement it.

Re:Browser Vulnerability to Superfish: A Fact-Finding Trip t... by patcheudor on Thursday February 19, 2015 @11:07PM (#9078860)
Ding, ding, ding. ;-)
Re:Browser Vulnerability to Superfish: A Fact-Finding Trip t... by mattlong on Friday February 20, 2015 @01:50PM (#9082102)
This is bumming me out. I'm really curious about what the exploit is but cannot quite put the pieces together...
Re:Browser Vulnerability to Superfish: A Fact-Finding Trip t... by jasonyan on Friday February 20, 2015 @10:29PM (#9084553)
Looks like someone already wrote a post about it: https://blog.filippo.io/komodia-superfish-ssl-validation-is-...
Re:Browser Vulnerability to Superfish: A Fact-Finding Trip t... by patcheudor on Friday February 20, 2015 @08:11PM (#9084200)
I hope to have a write-up at some point in the near future. I'm working with the vendor now to fix the vulnerability and hope they will be agreeable to a co-authored write-up once they've issued patches.
Re:Browser Vulnerability to Superfish: A Fact-Finding Trip t... by hellbanner on Friday February 20, 2015 @12:16AM (#9079057)
I'm really just curious & not malicious - is that string at the end of your post a hash of a key or of an exploit code?
Re:Browser Vulnerability to Superfish: A Fact-Finding Trip t... by octo_t on Friday February 20, 2015 @06:04AM (#9079920)
Its probably the hash of their explanation of the exploit.
Re:Browser Vulnerability to Superfish: A Fact-Finding Trip t... by ryan-c on Friday February 20, 2015 @10:56AM (#9080905)
correct
Re:Browser Vulnerability to Superfish: A Fact-Finding Trip t... by hellbanner on Friday February 20, 2015 @03:15PM (#9082691)
Then it must be a simple to phrase exploit with only one obvious way of stating it.
Re:Browser Vulnerability to Superfish: A Fact-Finding Trip t... by jongraehl on Saturday February 21, 2015 @01:16PM (#9086287)
The purpose of a publicized hash is that you can produce the content later and assert that you had authored it prior to the time you publicized the hash. This is proof to the extent that generating text to hit a given hash is really hard.
Re:Browser Vulnerability to Superfish: A Fact-Finding Trip t... by patcheudor on Thursday February 19, 2015 @09:34PM (#9078575)
Does anyone have a security contact at Superfish? It looks like they don't have a security@ mailbox:

"DB3FFO11OLC004.mail.protection.outlook.com rejected your message to the following email addresses:

[email protected] Something went wrong and your message couldn't be delivered. This could be a temporary issue. Try resending the message in a few minutes. If that doesn't work, forward this message to your email admin."

Re:Browser Vulnerability to Superfish: A Fact-Finding Trip t... by nadams on Thursday February 19, 2015 @10:05PM (#9078670)
Try abuse or postmaster or one of these:

http://whois.domaintools.com/superfish.com

Re:Browser Vulnerability to Superfish: A Fact-Finding Trip t... by patcheudor on Thursday February 19, 2015 @11:39PM (#9078957)
[email protected] went through and I'd imagine that they must be reading this thread by now and can go check that mailbox to reach out to me.
Re:Browser Vulnerability to Superfish: A Fact-Finding Trip t... by cbd1984 on Saturday February 21, 2015 @11:58AM (#9086025)
Article is unmarked PDF
Re:Browser Vulnerability to Superfish: A Fact-Finding Trip t... by cbd1984 on Saturday February 21, 2015 @01:00PM (#9086228)
PDF