A transit Linux host has a root-run maintenance job that invokes a command by relative name while PATH can be influenced insecurely. What risk class should the tester document?
Select an answer to reveal the explanation.
Short Explanation
If root shouts "run backup" without saying which hallway, someone may plant a fake backup first. Relative commands plus a sloppy PATH under root are a PATH hijack class — concept only, no recipes. Hostnames do not fix lookup order.
Full Explanation
Privileged jobs that invoke programs by relative name inherit PATH search order; an insecure or writable PATH can cause unexpected binaries to run as root. Testers should identify this PATH/relative-execution misconfiguration class conceptually and recommend absolute paths plus locked-down environments. Cron and other schedulers do honor PATH behavior. Cosmetic hostname traits are irrelevant to the control gap.