3 ms·
Well that depends entirely on wether you've configured your environment securely. If your sql server runs as an unprivileged user preferably on a different mach
by tinco 14y ago
Well that depends entirely on wether you've configured your environment securely. If your sql server runs as an unprivileged user preferably on a different machine this should not be an issue.
- tptacek 14y agoUh huh.
- tinco 14y agoSo you obviously don't agree, care to elaborate? You seem to be the expert here.. (btw I don't mean that command execution is not a problem, I mean that if you configure your sql server well it should not allow command execution, there's not _that_ many ways to escape the database..)
- tptacek 14y agoThis is one of those discussion where when I point out mistakes that (a) everyone makes and (b) you haven't thought of before and (c) are exploitable whether or not you encrypt, you're going to say "oh, well, you just shouldn't make those mistakes", and so I'm not interested in pursuing this and am content to rest my case.
- patio11 14y agoEven if someone were impressively thoughtful about that, they'd still cough up arbitrary code execution on the web tier for most Rails / Django applications, by writing an appropriately serialized external command into the queuing system. That external command would be loading metasploit into /tmp and then gaining root with a local privilege escalation. Thomas is right, though: if you lose the DB, you're forked.