CWE-648 - Incorrect Use of Privileged APIs
CWE-648 Low
- Abstraction:
- Base
- Structure:
- Simple
- Status:
- Incomplete
- Weakness Name
Incorrect Use of Privileged APIs
- Description
The product does not conform to the API requirements for a function call that requires extra privileges. This could allow attackers to gain privileges by causing the function to be called incorrectly.
When a product contains certain functions that perform operations requiring an elevated level of privilege, the caller of a privileged API must be careful to: If the caller of the API does not follow these requirements, then it may allow a malicious user or process to elevate their privilege, hijack the process, or steal sensitive data. For instance, it is important to know if privileged APIs do not shed their privileges before returning to the caller or if the privileged function might make certain assumptions about the data, context or state information passed to it by the caller. It is important to always know when and how privileged APIs can be called in order to ensure that their elevated level of privilege cannot be exploited.
- Common Consequences
Scope: Access Control
Impact: Gain Privileges or Assume Identity
Notes: An attacker may be able to elevate privileges.
Scope: Confidentiality
Impact: Read Application Data
Notes: An attacker may be able to obtain sensitive information.
Scope: Integrity, Confidentiality, Availability
Impact: Execute Unauthorized Code or Commands
Notes: An attacker may be able to execute code.
- Related Weaknesses
- Release Date:
- 2008-01-30
- Latest Modification Date:
- 2023-06-29
Free security scan for your website