CWE-1073
Weakness ProhibitedNon-SQL Invokable Control Element with Excessive Number of Data Resource Accesses
Abstraction: Base · Status: Incomplete
The product contains a client with a function or method that contains a large number of data accesses/queries that are sent through a data manager, i.e., does not use efficient database capabilities.
Mapping guidance
This entry is primarily a quality issue with no direct security implications.
Look for weaknesses that are focused specifically on insecure behaviors that have more direct security implications.
Modes of introduction
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
Notes
Terminology
While the interpretation of "large number of data accesses/queries" may vary for each product or developer, CISQ recommends a default maximum of 2 data accesses per function/method. [REF-1133]
Content history
Entry derived from Common Quality Enumeration (CQE) Draft 0.9.
updated Description, Relationships
updated Relationships
updated Description
updated References, Relationships
updated Mapping_Notes
updated Mapping_Notes
updated Applicable_Platforms
updated Common_Consequences, Description, Time_of_Introduction
updated Description, Detection_Factors, References, Terminology_Notes
0 vulnerabilities reference this CWE, most recent first.
No vulnerabilities reference this CWE.
No mitigation information available for this CWE.
No CAPEC attack patterns related to this CWE.