Re:Cache across domains with a file hash
by alexchamberlain on Thursday September 13, 2012 @09:36AM
(#4516034)
If you could find a malicious file that had the same hash as the current jQuery before the next one was released, then yes. I don't think this is possible, but I'm no expert!
[ Parent
| on HN ]
Re:Cache across domains with a file hash
by RyanMcGreal on Thursday September 13, 2012 @10:10AM
(#4516186)
"If you fear SHA-256 collisions but do not keep with you a loaded shotgun at all times, then you are getting your priorities wrong." http://stackoverflow.com/a/4681221
Re:Cache across domains with a file hash
by jefffoster on Thursday September 13, 2012 @10:18AM
(#4516230)
I think that quote is appropriate if you fear collisions with your own data set. The worry with a cache scheme like this is people would be actively seeking to find cache collisions.
Re:Cache across domains with a file hash
by alexchamberlain on Thursday September 13, 2012 @10:23AM
(#4516250)
That answer clearly explains why you can't, using current techniques and hardware.
Re:Cache across domains with a file hash
by Dylan16807 on Thursday September 13, 2012 @10:59AM
(#4516447)
> current techniques
We're talking about a long-term standard.
Re:Cache across domains with a file hash
by Jailbird on Thursday September 13, 2012 @09:38AM
(#4516042)
I guess I was thinking it'd be used for much more than just jQuery, and fast. Then for anything that any site wanted cached, some other site could essentially grab it if all they had was the hash.
Re:Cache across domains with a file hash
by alexchamberlain on Thursday September 13, 2012 @09:41AM
(#4516053)
Not sure I understand. How would another site grab it? And if they imported it into their page, why would that matter?
Re:Cache across domains with a file hash
by saalweachter on Thursday September 13, 2012 @10:13AM
(#4516201)
If I'm reading it correctly, I think the idea is, imagine your bank uses a hash-cache of an AJAX request containing your bank statements (stupid, yeah, but everyone is stupid sometimes).
A malicious website could then include a request to download a bogus URL from their site with a hash which matched that of the bank statement AJAX response. The browser would then return the cached bank statement, without ever noticing the URLs were bogus or didn't even point to a file with the desired hash. The malicious website could then upload the bank statements back to itself.
This seems like technically an attack path, but it relies on being able to guess a 256-bit hash in a relatively small number of guesses; if you can do that, you might as well just start guessing password hashes and log in to a target website directly.