A municipal host has a custom script wrapper marked SUID root that is not a standard system binary. What should the tester conclude?
Select an answer to reveal the explanation.
Short Explanation
A homemade "run me as root" badge on a script wrapper deserves a hard look. Unusual SUID/SGID programs are high-value enum targets — the kernel does not bless custom wrappers just for existing. Filename vibes are not a risk model.
Full Explanation
SUID and SGID bits on non-standard binaries or script wrappers elevate execution context and are classic Linux privilege-escalation enumeration targets. Testers should inventory unusual setuid programs and assess them as misconfiguration or weak-wrapper classes without shipping PoCs. The kernel does not automatically neutralize custom SUID tools. Ignoring such findings based on filenames understates risk.