CWE-648: Incorrect Use of Privileged APIs
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.
View on MITREExtended Description
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: ensure that assumptions made by the APIs are valid, such as validity of arguments account for known weaknesses in the design/implementation of the API call the API from a safe context 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.
Technical Details
- Structure
- Simple
Applicable To
Security Consequences
Scope
Impact
An attacker may be able to elevate privileges.
Scope
Impact
An attacker may be able to obtain sensitive information.
Scope
Impact
An attacker may be able to execute code.
Mitigation Strategies
Phase
Description
Before calling privileged APIs, always ensure that the assumptions made by the privileged code hold true prior to making the call.
Phase
Description
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.
Phase
Description
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.
Phase
Description
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.
Phase
Description
Only call privileged APIs from safe, consistent and expected state.
Phase
Description
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).
Detection Methods
No detection method information available for this CWE.
Code Examples & CVEs
Observed CVE Examples (1)
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.
View DetailsCWE Relationships
No relationship information available for this CWE.
Frequently Asked Questions
What is CWE-648: Incorrect Use of Privileged APIs?+
CWE-648: Incorrect Use of Privileged APIs is a Common Weakness Enumeration (CWE) entry maintained by MITRE. 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: ensure that assumptions made by the APIs are valid, such as validity of arguments account for known weaknesses in the design/implementation of the API call the API from a safe context 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.
What are the security consequences of Incorrect Use of Privileged APIs?+
If exploited, CWE-648 (Incorrect Use of Privileged APIs) it can compromise Access Control, Confidentiality, Integrity and Availability, leading to outcomes such as Gain Privileges or Assume Identity, Read Application Data and Execute Unauthorized Code or Commands.
How do you prevent or mitigate Incorrect Use of Privileged APIs?+
Recommended mitigations for CWE-648 include: 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.
Which programming languages are affected by Incorrect Use of Privileged APIs?+
CWE-648 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.
What are real-world examples of Incorrect Use of Privileged APIs?+
MITRE documents real CVEs mapped to CWE-648, including CVE-2003-0645. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.
What is the difference between a CWE and a CVE?+
A CWE (Common Weakness Enumeration) like CWE-648 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.