Why is it often effective to check for 'Capabilities' on Linux binaries when SUID is not present?
Capabilities break down root privileges into smaller units. If a binary is granted the 'CAP_DAC_OVERRIDE' capability, for example, it can bypass file permission checks even if the binary itself isn't running as root. This allows for privilege escalation by leveraging the binary's authorized, high-level permissions.
Why this answer
Linux capabilities allow for fine-grained control over privileged operations, such as network raw socket access or file modification, without requiring the full root user. If a binary has excessive capabilities assigned, it can be abused to perform privileged actions. This is a subtle but powerful alternative to SUID that is frequently overlooked during security assessments, making it a valuable path for privilege escalation when traditional SUID targets are unavailable.
Exam trap
Students often ignore binaries lacking the SUID bit entirely, assuming they are secure, and completely overlook alternative mechanisms like Linux capabilities during enumeration.