4 ms·
TLDR: Send spoofed TCP package with HTTP redirect to malicious site right after victim does a GET request. This attack, while impressive and nifty, would seem
by dtech 12y ago
TLDR: Send spoofed TCP package with HTTP redirect to malicious site right after victim does a GET request.
This attack, while impressive and nifty, would seem to be easily subverted by SSL right?* Yet another example that shows that non-SSL HTTP should be phased out.
* In the ideal situation where users check URL's and the CA system is good enough to keep the NSA out.
- ilaksh 12y agoWhy shouldn't we assume the NSA has subverted the CA system? Why would we all rely on central authority for security if not to support centralized surveillance?
- Dylan16807 12y agoBecause that subversion can be relatively easily detected, and then shouted to the world.
- motoboi 12y agoGiven the episode where stolen Realtek certificates been used for years by a government-made malware, I think we should not be so sure that they can't do that. A single request going through a bogus certificate emitted by NSA "acquired" CA would be hardly detected. Or, given the fact that they could indeed broke keys, they could simply do a man-in-the-middle, instead of a man-in-the-side.
- Dylan16807 12y agoA stolen key is a server-being-hacked problem, not a CA problem. If the server is hacked, game over. There are browser extensions that detect bogus certificates; there's a good risk of catching them.
- SG- 12y agoShould we pretend the NSA and various organizations don't have the means to infiltrate a CA?
- Karunamon 12y agoAgain, pinning is a realistic countermeasure to this.
- motoboi 12y agoCertificate Authorities normally run as software on a box somewhere. Sometimes they keep this box offline, but they need to keep a sub-CA online somewhere, or they wouldn't be able to issue certificates. So, a CA private key and public certificate can be compromised in much the same way a single server certificate. With a CA private key and public certificate, one can easily emit a bogus certificate for *.google.com or any other domain name. If this CA public certificate is trusted by the browser, a user would hardly notice.
- un1xl0ser 12y agoOr they crack or compromise the keys that they need on a per operation bases. Even assuming ubiquitous SSL (or something more decentralized), the keys of a few advertising or web analytics sites would get a lot of coverage. Creative use of advertising platforms is used you could easily narrow targets down and guarantee that you know exactly what the content is. Anyways, this is just one gadget.
- chopin 12y agoThen you must replace all traffic to that site successfully. The keys for the spoofed and the legitimate certificate will be different. With PFS only traffic with the negotiated key can be decrypted by the browser. Without PFS, the legitimate server will not understand your requests. Quantum Insert is not successful for each request, as stated by the article. Therefore I would assume that at least a few packages of the original server would slip through which then cannot be decrypted or contain an error message of the server. Especially targeted administrators would notice very quickly, I assume (although browsers might suppress those packages silently). Therefore this would work only with a full man-in-the-middle. I think in general https would work against this particular attack, if you don't accept sites with mixed content (I am not aware of any browser plugin which does suppress plain content on mixed sites).
- jerf 12y ago"Why shouldn't we assume the NSA has subverted the CA system?" Broadly speaking, we should. And that's why there's been a lot of work lately in doing things that either build on or bypass the CA system. For instance, even if you get a valid CA certificate for a site you want to spoof, it still has to be a different certificate, so there's more work on certificate pinning. Sure, that doesn't help if the spoof cert is up the first time a given person visits a site, but it still raises the bar for successfully attacking a site surreptitiously, because anyone who hits the site post-pin will get a big warning, which can be picked up with other things. Now the attack has to be even better targeted. And there's other work going on lately, and while it may not be immediately visible to the general public because this all takes time, it really seems to me this has all gotten a lot more vigorous over the last year. I don't even think it's all Snowden per se... it seems to me generalized security consciousness has gone up lately, like we passed a critical threshold of people's work feeding back on other people's work and the community as a whole has moved to a new level of effectiveness. It'll still be a while before we really see the changes but I think some changes are coming. (Not Utopia. We've still got a long ways to go. But some general improvements.)
- wahsd 12y agoIt has been. If I recall correctly it was revealed even years before Manning and Wikileaks. As a matter of observation, it is kind of amazing how short of a memory even the internet has. It seem to be a knowledge management issue, i.e., new and evolving information is not contextualized or even related to pertinent past information.
- RKearney 12y agoNot to nit-pick here, but SSL has its own set of vulnerabilities and should no longer be used. Most sites today are using TLS and phasing out of SSL.
- lbearl 12y agoI think contemporary parlance pretty much has TLS and SSL as synonyms, as they are effectively two means to achieving the same ends.