3 ms·
If this was even a remotely feasible problem with modern cryptographic hashes, DNSSEC, TLS, SSH, package management systems, most authentication systems, etc. w
by ctz 11y ago
If this was even a remotely feasible problem with modern cryptographic hashes, DNSSEC, TLS, SSH, package management systems, most authentication systems, etc. would all be dramatically broken.
If I had this capability I wouldn't waste it on injecting javascript into web pages. I'd create forged browser upgrades and go from there.
- duaneb 11y agoCache poisoning is not necessarily breaking the hash, it just means they snuck something in there somehow (e.g. social engineering techniques).
- Dylan16807 11y agoIn this context it's cache poisoning that does require breaking the hash. Which is not a realistic reason to reject the concept.
- duaneb 11y ago...how would social engineering NOT work to distribute javascript vulnerabilities or backdoors via jquery??
- Dylan16807 11y agoEvery website using jquery will have the real hash, so you can poison all the mirrors you like and it won't matter. The only way to get the wrong hash onto sites is to actually publish it on the authoritative server. That's not cache poisoning, that's a malicious official version.