Build fluency in the vocabulary of a low-privilege user exploiting a flaw to gain unearned elevated access.
0 / 5 completed
1 / 5
A teammate describes an attack where a user who only has limited, unprivileged access exploits a flaw to gain administrator-level control over a system, rather than being granted that access legitimately. What is this attack called?
Privilege escalation is exactly this: a user who only has limited, unprivileged access exploits a software or configuration flaw to gain administrator-level, or otherwise higher, access than they were legitimately granted. A hash collision is an unrelated hash-table concept about two keys sharing a bucket. This exploit-a-flaw-to-gain-unearned-access approach is exactly why privilege escalation is treated as a critical vulnerability class distinct from a legitimately provisioned admin account.
2 / 5
During a security review, the team discovers a low-privilege service account can exploit a misconfigured setuid binary to spawn a root shell, specifically without any legitimate grant of root access. Which risk does this represent?
This represents a privilege-escalation vulnerability, since the low-privilege account gains root-level control entirely through exploiting the flaw rather than through any legitimate grant. A service account intentionally configured with root access from the start would be a deliberate, auditable design decision, not an exploited flaw granting unearned control. This gain-unearned-root-via-flaw behavior is exactly why privilege escalation is flagged and patched as a critical vulnerability rather than accepted as normal access.
3 / 5
In a code review, a dev notices a setuid binary runs with root permissions and passes an unsanitized, attacker-controllable environment variable into a shell command it executes. What risk does this represent?
This is a privilege-escalation risk, since an attacker-controllable environment variable fed into a root-running shell command could let a low-privilege user execute arbitrary commands with root access. A cache eviction policy is an unrelated concept about discarded cache entries. This unsanitized-input-into-a-root-shell pattern is exactly the kind of vulnerability a reviewer flags once a binary runs with elevated permissions.
4 / 5
An incident report shows a low-privilege user gained a root shell by manipulating an unsanitized environment variable that a setuid root binary passed directly into a shell command it executed. What practice would prevent this?
Sanitizing or eliminating attacker-controllable input passed into any command executed by the setuid root binary closes off the privilege-escalation path through that input. Continuing to pass the unsanitized environment variable directly into the shell command the setuid root binary executes regardless of who can control it is exactly what let the low-privilege user gain root in this incident. This sanitize-privileged-input approach is the standard fix once an unsanitized-input escalation path is confirmed to exist.
5 / 5
During a PR review, a teammate asks why the team invests in hardening against privilege escalation instead of just trusting that low-privilege accounts will never be compromised in the first place. What is the reasoning?
Hardening against privilege escalation trades some extra validation and permission-scoping effort for containing the damage even after a low-privilege account is compromised, while trusting accounts to never be compromised ignores that any single account can eventually be breached through unrelated means such as phishing or leaked credentials. This is exactly why defense-in-depth against privilege escalation is standard practice, rather than relying solely on the hope that low-privilege accounts stay uncompromised.
What does the "Privilege Escalation Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to privilege escalation vocabulary through 5 multiple-choice questions, each built from realistic workplace sentences rather than abstract definitions.
Is this vocabulary exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 5 questions. Each one shows a real-world sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question, and a full results screen at the end.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Are these vocabulary exercises connected to other topics?
Yes — this module shares real-world context with 14 other vocabulary modules. See "Related vocabulary" below to keep building a connected skill set.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more vocabulary exercises?
Browse the full Vocabulary exercises hub for hundreds of modules covering Agile, DevOps, security, databases, architecture, and more — organised by IT role and skill.