CWE-648Incorrect 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.

[object Object]

Common consequences

• Access Control→Gain Privileges or Assume Identity
  An attacker may be able to elevate privileges.
• Confidentiality→Read Application Data
  An attacker may be able to obtain sensitive information.
• Integrity,Confidentiality,Availability→Execute Unauthorized Code or Commands
  An attacker may be able to execute code.

Potential mitigations

• Implementation
  Before calling privileged APIs, always ensure that the assumptions made by the privileged code hold true prior to making the call.
• Architecture and Design
  Know architecture and implementation weaknesses of the privileged APIs and make sure to account for these weaknesses before calling the privileged APIs to ensure that they can be called safely.
• Implementation
  If privileged APIs make certain assumptions about data, context or state validity that are passed by the caller, the calling code must ensure that these assumptions have been validated prior to making the call.
• Implementation
  If privileged APIs do not shed their privilege prior to returning to the calling code, then calling code needs to shed these privileges immediately and safely right after the call to the privileged APIs. In particular, the calling code needs to ensure that a privileged thread of execution will never be returned to the user or made available to user-controlled processes.
• Implementation
  Only call privileged APIs from safe, consistent and expected state.
• Implementation
  Ensure that a failure or an error will not leave a system in a state where privileges are not properly shed and privilege escalation is possible (i.e. fail securely with regards to handling of privileges).

Related CWEs

Recent CVEs classified under this CWE