Re:A single byte write opened a root execution exploit
by uola on Saturday October 15, 2016 @07:55AM
(#12713652)
I don't think one should mix validation and safety as such since it risks becoming non-obvious. When the validation criteria changes six month later someone might rewrite the validation without considering that it's also a safety feature. By making the proper way to use it restrictive one might end up bypassing the validation and using the unsafe part by re-implementation if not directly. It could also be that the error isn't malicious, but that the hash for some reason ends up being faulty.
Re:A single byte write opened a root execution exploit
by umanwizard on Saturday October 15, 2016 @12:48PM
(#12714636)
Yep, that's all true -- this type of attack can be mitigated in various easy ways. But there are lots of other examples where writing one byte can break a system. I was just trying to prove the point by showing a particularly simple one.
Then you might still get some mileage out of it (you'd be able to shorten the password).
You'd also hope that in all production systems live at the moment the passwords stored would not be in plaintext but properly hashed so writing random nuls into either one of the hashes would simply result in a mismatch.