Difference between revisions of "Often Misused: Privilege Management"

From OWASP
Jump to: navigation, search
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
{{Template:Vulnerability}}
 
{{Template:Fortify}}
 
{{Template:Fortify}}
  
{{Template:Vulnerability}}
+
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
  
==Abstract==
+
[[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]
  
 +
==Description==
 
Failure to adhere to the principle of least privilege amplifies the risk posed by other vulnerabilities.
 
Failure to adhere to the principle of least privilege amplifies the risk posed by other vulnerabilities.
 
==Description==
 
  
 
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.
 
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.
Line 15: Line 15:
 
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.
 
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.
  
==Examples ==
 
  
==Related Threats==
+
==Risk Factors==
  
==Related Attacks==
+
TBD
  
[[:Category:API Abuse Attack]]
+
==Examples==
  
==Related Vulnerabilities==
+
TBD
  
==Related Countermeasures==
+
==Related [[Attacks]]==
  
==Categories==
+
* [[Attack 1]]
 +
* [[Attack 2]]
  
[[Category:Access Control Vulnerability]]
 
  
[[Category:Use of Dangerous API]]
+
==Related [[Vulnerabilities]]==
  
[[Category:Implementation]]
+
* [[Vulnerability 1]]
 +
* [[Vulnerabiltiy 2]]
  
 +
==Related [[Controls]]==
 +
 +
* [[Control 1]]
 +
* [[Control 2]]
 +
 +
 +
==Related [[Technical Impacts]]==
 +
 +
* [[Technical Impact 1]]
 +
* [[Technical Impact 2]]
 +
 +
 +
==References==
 +
 +
TBD
 +
 +
 +
__NOTOC__
 +
 +
 +
[[Category:OWASP ASDR Project]]
 +
[[Category:Authorization Vulnerability]]
 +
[[Category:Use of Dangerous API]]
 +
[[Category:Implementation]]
 
[[Category:Code Snippet]]
 
[[Category:Code Snippet]]
 +
[[Category:API Abuse]]
 +
[[Category:Vulnerability]]

Latest revision as of 08:08, 27 February 2009

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


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

Last revision (mm/dd/yy): 02/27/2009

Vulnerabilities Table of Contents

Description

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.


Risk Factors

TBD

Examples

TBD

Related Attacks


Related Vulnerabilities

Related Controls


Related Technical Impacts


References

TBD