CPSA ยท Unix user enumeration and mail/file services
Unix and Linux vulnerability classes
Remote and local exploit classes for root access and why patching and minimal services matter.
Key points
- Remote flaws sit in network-facing daemons (memory corruption, bad input handling, weak configuration) and can give access without an account.
- Local flaws need a foothold first and escalate privileges through SUID programs, kernel bugs, weak file permissions or misconfigured scheduled jobs.
- Prompt patching and running only the services you need shrink both.
Practice questions
Which practice most directly protects against already-known, publicly exploited flaws?
- Applying vendor security patches promptly
- Hiding version strings in banners only
- Renaming the root account
- Using longer hostnames
Show answer
Answer: A. Applying vendor security patches promptly
Vendor patches fix known flaws at the source. Longer banners, renamed accounts and hidden version strings change nothing about the vulnerable code.
Which findings are typical routes to local privilege escalation on Unix?
- A vulnerable SUID-root program
- A world-writable script run by root from cron
- An unpatched kernel with a known local flaw
- ICMP echo replies enabled
- A long login banner
Show answer
Answer: A. A vulnerable SUID-root program, B. A world-writable script run by root from cron, C. An unpatched kernel with a known local flaw
Vulnerable SUID programs, writable scripts run by root and unpatched kernels are classic routes. An open ICMP echo and a long banner give an attacker nothing for escalation.
A remote exploit against a daemon running as root can only give the attacker an unprivileged shell.
Show answer
Answer: False
False. Code that runs inside a process inherits that process's privileges, so a flaw in a root-owned daemon can hand over root directly. This is why daemons should drop privileges.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
