The product performs too many data queries without using efficient data processing functionality such as stored procedures.
This issue can make the product perform more slowly due to computational expense. If the relevant code is reachable by an attacker, then this performance problem might introduce a vulnerability.
While the interpretation of "too many data queries" may vary for each product or developer, CISQ recommends a default maximum of 5 data queries for an inefficient function/procedure.
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| ChildOf | Allowed-with-Review | C | 1120 | Excessive Code Complexity |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 1132 | CISQ Quality Measures (2016) - Performance Efficiency |
| MemberOf | Prohibited | C | 1226 | Complexity Issues |
| MemberOf | Prohibited | C | 1309 | CISQ Quality Measures - Efficiency |
| MemberOf | Prohibited | C | 1412 | Comprehensive Categorization: Poor Coding Practices |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | BS | BOSS-313 | Reduce Performance (impact) |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 1226 | Complexity Issues |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 1309 | CISQ Quality Measures - Efficiency |
| Scope | Likelihood | Impact | Note |
|---|---|---|---|
| Other | N/A | Reduce Performance | N/A |
| Reference | Description |
|---|
| Ordinality | Description |
|---|---|
| Indirect | N/A |
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.
| Taxonomy Name | Entry ID | Fit | Entry Name |
|---|---|---|---|
| OMG ASCPEM | ASCPEM-PRF-9 | N/A | N/A |
| ID | Name |
|---|