A county Linux host shows file capability bits granting a binary powerful privileges without a traditional SUID bit. What should the tester include in enumeration thinking?
Select an answer to reveal the explanation.
Short Explanation
Think of capabilities as giving someone a master key to one wing of the building instead of the whole campus. A binary can get dangerous rights without looking like classic SUID. Good Linux priv-esc enum checks capabilities alongside the usual suspects.
Full Explanation
Linux file capabilities assign fine-grained privileged operations to executables without requiring full root via SUID. Dangerous capabilities (for example those enabling raw sockets, DAC overrides, or setuid-related behavior) are a recognized privilege-escalation enumeration target. They do not replace reviewing sudoers, scheduled jobs, or writable service paths—they complement that checklist. Treating capabilities as Windows-only or as proof of sandboxing misses the risk class.