Re:Select Code_execution from * Using SQLite; (2019)
by c22 on Saturday June 13, 2020 @04:45PM
(#23512548)
I am not convinced. If your software is secured with any sort of key then you can break this with brute force also. All other attempts to prevent unauthorized access are applications of varying degrees of obfuscation and indirection, the same as in physical lock design.
[ Parent
| on HN ]
Re:Select Code_execution from * Using SQLite; (2019)
by anyfoo on Saturday June 13, 2020 @05:05PM
(#23512727)
That is not how privilege boundaries work.
Re:Select Code_execution from * Using SQLite; (2019)
by c22 on Saturday June 13, 2020 @06:02PM
(#23513170)
Then how do explain privilege escalation attacks other than as a user discovering a path to elevated privileges that was not anticipated by the designers? Can't you "brute force" even the most theoretically rock solid privilege boundary by simply attaching your own computer to the memory in question?
Re:Select Code_execution from * Using SQLite; (2019)
by anyfoo on Saturday June 13, 2020 @10:20PM
(#23514599)
> other than as a user discovering a path to elevated privileges that was not anticipated by the designers
Most of the time, a barrier to elevated privileges that was not correctly implemented, i.e. a bug, not anything the designer did not anticipate.
> Can't you "brute force" even the most theoretically rock solid privilege boundary by simply attaching your own computer to the memory in question?
So? Does that mean it's not worth looking at the paths where the attacker does not have physical access of the machine that sits in some data center's secured basement?