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.
[ Parent
| on HN ]
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.