I think you have to give the author a little credit. Sometimes developers pick a non-cryptographic hash and they don't realize they actually need collision resi

I think you have to give the author a little credit. Sometimes developers pick a non-cryptographic hash and they don't realize they actually need collision resistance, e.g. because an attacker-controlled input can cause an O(1) hash table operation to go O(n). These kinds of articles are great for red teams, since they actually have to demonstrate the problem instead of just switching out the algorithm.