SecurCheckCyber Center
Need help
Back to analysis tools
All cyber threats
Infrastructure

Infrastructure privilege escalation

Linux root escalation, Windows administrator privilege escalation, local privilege escalation

Privilege escalation is the exploitation of a vulnerability, excessive permission or exposed credential that lets an attacker turn limited access to a server or infrastructure into administrative or root-level control.

Fiche de sensibilisationPrête à diffuser à vos équipes ou clients

MIGHT YOU BE AFFECTED?

Turn knowledge into action.

How does this work?

An account or process with restricted rights may reach resources reserved for administrators when a system contains an unpatched local vulnerability, a misconfigured privileged executable, unsafe sudo policy, overprivileged service account, writable service definition or leaked administrative secret. Escalation often follows an initial compromise; it is not by itself proof that unauthenticated remote access was possible.

REAL-WORLD EXAMPLE

« An attacker first compromises a low-privilege web application account on a Linux server. A misconfigured privileged executable or permissive sudo rule then allows that account to execute a command as root and change security settings. »

Typical sequence

  1. 1An attacker obtains an initial foothold as a limited user, service account or containerised process.
  2. 2They enumerate accessible files, permissions, sudo rules, privileged binaries, running services or local vulnerabilities.
  3. 3They exploit a specific weakness or misconfiguration to gain administrator, root, SYSTEM or another more powerful role.
  4. 4With the new privileges, they may disable protections, access secrets, create persistence or move to other systems.

Warning signs

  • Unexpected sudo, su, setuid or privileged-process execution by application or service accounts.
  • An unexplained addition to an administrators group, privileged role or cloud IAM policy.
  • Creation of new privileged accounts, scheduled tasks, services or persistence mechanisms.
  • Changes to system binaries, sudoers rules, permissions or security-agent configuration.
  • Privilege assignments or authentication events inconsistent with the normal deployment process.

How to protect yourself

  • Apply vendor-approved operating-system, kernel and application security patches promptly.
  • Enforce least privilege for users, service accounts, containers and automation identities.
  • Review sudo, setuid and setgid permissions, local administrators, service definitions and privileged cloud roles.
  • Use PAM, strong authentication and privileged access controls for high-risk administrative operations.
  • Monitor audit logs, privilege changes, unusual parent-child process relationships and endpoint detections.
  • Keep production application processes separate from administrative accounts and restrict access to secrets.

If you think you are affected

Isolate the affected host or workload in a controlled way and preserve relevant forensic evidence. Revoke newly assigned privileges, disable attacker-created accounts and persistence, rotate potentially exposed secrets and establish the initial entry point. Patch the exploited weakness or permission error and verify whether other machines were accessed. For high-confidence compromise with root or administrator access, prefer rebuilding from a trusted image rather than relying only on removal of suspicious files.

Get help

Last updated: 8 October 2026