CWE-1177
Weakness Allowed-with-ReviewUse of Prohibited Code
Abstraction: Class · Status: Incomplete
The product uses a function, library, or third party component that has been explicitly prohibited, whether by the developer or the customer.
Mapping guidance
This CWE entry is a Class and might have Base-level children that would be more appropriate
Examine children of this entry to see if there is a better fit
Modes of introduction
To reduce risk of vulnerabilities, the developer - or customers - may wish to restrict or eliminate use of a function, library, or third party component for any number of reasons, including real or suspected vulnerabilities; difficulty to use securely; export controls or license requirements; obsolete or poorly-maintained code; internal code being scheduled for deprecation; etc. This might be achieved using a list of "banned" functions that programmers must avoid using, because the functions are difficult or impossible to use securely.
Detection methods
Automated Static Analysis
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
Effectiveness: High
Content history
updated References, Relationships
updated Description
updated References, Relationships, Time_of_Introduction
updated Mapping_Notes
updated Demonstrative_Examples, Observed_Examples
updated Applicable_Platforms, Detection_Factors
updated Potential_Mitigations, References
updated Common_Consequences, Description, Modes_of_Introduction, Time_of_Introduction
0 vulnerabilities reference this CWE, most recent first.
No vulnerabilities reference this CWE.
Mitigation MIT-58
Identify a list of prohibited API functions and prohibit developers from using these functions, providing safer alternatives. In some cases, automatic code analysis tools or the compiler can be instructed to spot use of prohibited functions, such as the "banned.h" include file from Microsoft's SDL. [REF-554] [REF-1009] [REF-7]
No CAPEC attack patterns related to this CWE.