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.
Potential Impact
Access Control
Gain Privileges or Assume Identity
Confidentiality
Read Application Data
Integrity, Confidentiality, Availability
Execute Unauthorized Code or Commands
Mitigations & Prevention
Before calling privileged APIs, always ensure that the assumptions made by the privileged code hold true prior to making the call.
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.
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.
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.
Only call privileged APIs from safe, consistent and expected state.
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).
Real-World CVE Examples
| CVE ID | Description |
|---|---|
| CVE-2003-0645 | A Unix utility that displays online help files, if installed setuid, could allow a local attacker to gain privileges when a particular file-opening function is called. |
Related Weaknesses
Frequently Asked Questions
What is CWE-648?
CWE-648 (Incorrect Use of Privileged APIs) is a software weakness identified by MITRE's Common Weakness Enumeration. It is classified as a Base-level weakness. 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.
How can CWE-648 be exploited?
Attackers can exploit CWE-648 (Incorrect Use of Privileged APIs) to gain privileges or assume identity. This weakness is typically introduced during the Architecture and Design, Implementation, Operation phase of software development.
How do I prevent CWE-648?
Key mitigations include: Before calling privileged APIs, always ensure that the assumptions made by the privileged code hold true prior to making the call.
What is the severity of CWE-648?
CWE-648 is classified as a Base-level weakness (Medium abstraction). It has been observed in 1 real-world CVEs.