Non-SQL Invokable Control Element with Excessive Number of Data Resource Accesses
Incomplete Base
Structure: Simple
Description
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.
This issue can make the product perform more slowly. If the relevant code is reachable by an attacker, then this performance problem might introduce a vulnerability. 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.
Common Consequences 1
Scope: Other
Impact: Reduce Performance
References 1
Automated Source Code Performance Efficiency Measure (ASCPEM)
Object Management Group (OMG)
01-2016
https://www.omg.org/spec/ASCPEM/(2023-04-07)
ID: REF-959
Applicable Platforms
Languages:
SQL : Often
Technologies:
Database Server : Often
Related Weaknesses
Taxonomy Mapping
- OMG ASCPEM