3 ms·
So if your server is set up with limited permissions for the apache-user, are you still at risk? I don't think the apache-user if properly restricted can write
by mrfusion 12y ago
So if your server is set up with limited permissions for the apache-user, are you still at risk?
I don't think the apache-user if properly restricted can write to directories, or even read most of the system files?
- efdee 12y agoApache user can probably write to /tmp, and from there the attacker can construct a way into the system (bindshell, reverse shell). He can then start reading your PHP config files (db passwords) or try to use other vulnerabilities to escalate his privileges.
- mrfusion 12y agoIsn't it kind of a security best practice to assume your web user can be compromised and plan accordingly with permissions?
- Timothee 12y agoFrom the article, it sounds like the issue is not just with Apache but also ssh, DHCP and others. So I'd just assume you're still at risk regardless of your Apache user configuration. (in any case, it's safer to act as if)
- sneak 12y agoIt can read your application source code, read your database credentials, access your database, and exfiltrate its contents. Yes, you are at risk.
- acdha 12y agoThings like that lower the risk: run everything as a low-privilege account (better, not even www-data but per-site), chroot()-ed, etc. and certain classes of attack will either fail or at least be easier to clean up. The problem with all of this is that it assumes that you don't have privilege escalation vulnerabilities on the local system, which is often not the case unless non-trivial effort has gone into hardening the server – e.g. all of that privilege separation is a waste if someone sledgehammer-ed a chmod 777 into a script rather than setting the appropriate ownership and permissions or someone delayed a kernel update because they didn't want the downtime and “knew” that only trusted code ran on that system.
- drzaiusapelord 12y agoIt doesn't seem to have trouble writing to /tmp in a typical low access scenario. Seems to me, anything can write to /tmp. Default seems to be 777 on /tmp. I had someone exploit my Pydio install a few months ago with a litecoin miner. He managed to drop and run it in /tmp. He probably couldn't write and execute to too many other places.