Quick Answer
The answer is to use vim's shell escape via `:!bash` to get a root shell. This works because when a user has sudo rights to run `/usr/bin/vim` as root without a password, vim inherits root privileges, and its built-in `:!` command allows executing arbitrary shell commands from within the editor, effectively spawning a root shell. On the Certified Ethical Hacker CEH exam, this tests your understanding of sudo privilege escalation vectors, specifically how trusted binaries with shell escape capabilities can be exploited. A common trap is forgetting that vim’s `:!` is not just for running external programs but can directly launch a shell; many students mistakenly try to edit `/etc/sudoers` instead. Remember the mnemonic “Vim’s bang gives you the hang” — typing `:!bash` inside vim as sudo hands you a root shell instantly.
This CEH practice question tests your understanding of enumeration and system hacking. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A penetration tester gains access to a Linux server and attempts to escalate privileges. They run `sudo -l` and see that the user can run `/usr/bin/vim` as root without a password. Which privilege escalation technique should the tester use?
Perform token impersonation using SeImpersonatePrivilege
Why wrong: This is Windows-specific.
Use vim's shell escape via `:!bash` to get a root shell
Vim can spawn a shell that runs with root privileges if launched via sudo.
Exploit a kernel vulnerability (CVE-2023-xxxx)
Why wrong: No need for kernel exploit when sudo misconfiguration is present.
Abuse the SUID bit on vim
Why wrong: SUID bit is not set; sudo allows running as root.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Use vim's shell escape via `:!bash` to get a root shell
If a user has sudo rights to run vim as root, they can escape to a shell by typing `:!bash` within vim, gaining a root shell. This is a known sudo privilege escalation vector.
Key principle: Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Perform token impersonation using SeImpersonatePrivilege
Why it's wrong here
This is Windows-specific.
Use vim's shell escape via `:!bash` to get a root shell
Why this is correct
Vim can spawn a shell that runs with root privileges if launched via sudo.
Related concept
Authentication checks who the user is.
Exploit a kernel vulnerability (CVE-2023-xxxx)
Why it's wrong here
No need for kernel exploit when sudo misconfiguration is present.
Abuse the SUID bit on vim
Why it's wrong here
SUID bit is not set; sudo allows running as root.
Common exam traps
Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.
Detailed technical explanation
This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.
Key takeaway
Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
Real-world example
A small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
What to study next
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related CEH questions on access control and AAA configuration.
Enumeration and System Hacking — study guide chapter
Learn the concepts, then practise the questions
Enumeration and System Hacking practice questions
Targeted practice on this topic area only
All CEH questions
1,010 questions across all exam domains
Certified Ethical Hacker CEH study guide
Full concept coverage aligned to exam objectives
CEH practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise CEH questions linked to Footprinting, Reconnaissance and Scanning.
Practise CEH questions linked to Enumeration and System Hacking.
Practise CEH questions linked to Malware, Social Engineering and Network Attacks.
Practise CEH questions linked to Web Application and Injection Attacks.
Practise CEH questions linked to Introduction to Ethical Hacking.
Practise CEH questions linked to Scanning Networks and Enumeration.
Practise CEH questions linked to Vulnerability Analysis and System Hacking.
Practise CEH questions linked to Advanced Topics: Wireless, Cloud, IoT, Cryptography.
Practise CEH questions linked to Footprinting and Reconnaissance.
Practise CEH questions linked to Network and Web Application Attacks.
Practise CEH questions linked to Wireless, IoT and Cloud Security.
Practise CEH questions linked to Cryptography and Malware Analysis.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Enumeration and System Hacking — This question tests Enumeration and System Hacking — Authentication checks who the user is..
The correct answer is: Use vim's shell escape via `:!bash` to get a root shell — If a user has sudo rights to run vim as root, they can escape to a shell by typing `:!bash` within vim, gaining a root shell. This is a known sudo privilege escalation vector.
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related CEH questions on access control and AAA configuration.
Authentication checks who the user is.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Keep practising
Last reviewed: Jun 21, 2026
This CEH practice question is part of Courseiva's free EC-Council certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CEH exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.