Owner of special device not checked, allowing root.
Related Attack Patterns (CAPEC)
N/A
Attack TTPs
N/A
Modes of Introduction
Phase
Note
Architecture and Design
REALIZATION: This weakness is caused during implementation of an architectural security tactic.
Common Consequences
Impact: Gain Privileges or Assume Identity — Notes: An attacker could gain unauthorized access to system resources.
Potential Mitigations
Architecture and Design: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software. (N/A)
Architecture and Design: Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource. (N/A)
Applicable Platforms
None (Not Language-Specific, Undetermined)
Demonstrative Examples
Intro: This function is part of a privileged program that takes input from users with potentially lower privileges.
Body: This code does not confirm that the process to be killed is owned by the requesting user, thus allowing an attacker to kill arbitrary processes.