Difference between revisions of "Often Misused: Privilege Management"

Jump to: navigation, search
Line 20: Line 20:
==Related Attacks==
==Related Attacks==
[[:Category:API Abuse Attack]]
==Related Vulnerabilities==
==Related Vulnerabilities==
Line 36: Line 34:
[[Category:Code Snippet]]
[[Category:Code Snippet]]
[[Category:API Abuse]]

Revision as of 12:47, 18 July 2006

This article includes content generously donated to OWASP by Fortify.JPG.

This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.


Failure to adhere to the principle of least privilege amplifies the risk posed by other vulnerabilities.


Programs that run with root privileges have caused innumerable Unix security disasters. It is imperative that you carefully review privileged programs for all kinds of security problems, but it is equally important that privileged programs drop back to an unprivileged state as quickly as possible in order to limit the amount of damage that an overlooked vulnerability might be able to cause.

Privilege management functions can behave in some less-than-obvious ways, and they have different quirks on different platforms. These inconsistencies are particularly pronounced if you are transitioning from one non-root user to another.

Signal handlers and spawned processes run at the privilege of the owning process, so if a process is running as root when a signal fires or a sub-process is executed, the signal handler or sub-process will operate with root privileges. An attacker may be able to leverage these elevated privileges to do further damage.


Related Threats

Related Attacks

Related Vulnerabilities

Related Countermeasures