A transit agency service runs as root and loads its configuration from a directory writable by a low-privilege user. What privilege-escalation theme does that represent?
Select an answer to reveal the explanation.
Short Explanation
If root reads a config file you can edit, you are basically writing tomorrow morning's instructions for the boss. That writable-path-plus-privileged-reader pattern is a textbook Linux priv-esc theme. Keep hunting those paths instead of assuming confinement already fixed it.
Full Explanation
When a process running as root (or another high-privilege identity) consumes configuration, scripts, or plugins from a location writable by a lesser user, that user can often influence privileged execution. This is a standard Linux privilege-escalation misconfiguration class independent of whether systemd timers or seccomp exist elsewhere. Enumeration should continue; network pivoting does not replace fixing or reporting local writable service configs.