CWE-1060 Detalhe

The product performs too many data queries without using efficient data processing functionality such as stored procedures.

Modos de Introdução

Implementation
Architecture and Design

Plataformas Aplicáveis

Linguagem

Classe: Not Language-Specific (Undetermined)

Consequências Comuns

Métodos de Detecção

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.)
Eficácia : High

Notas de Mapeamento de Vulnerabilidade

Justificativa : This entry is primarily a quality issue with no direct security implications.
Comentário : Look for weaknesses that are focused specifically on insecure behaviors that have more direct security implications.

Notas

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. [REF-1133]

Referências

REF-959

Automated Source Code Performance Efficiency Measure (ASCPEM)
Object Management Group (OMG).
https://www.omg.org/spec/ASCPEM/

REF-1133

Automated Source Code Quality Measures
Consortium for Information & Software Quality (CISQ).
https://www.omg.org/spec/ASCQM/

REF-1534

Automated Technical Debt Measure, Version 2
OMG.
https://www.omg.org/spec/ATDM2/1.0/PDF

Submissão

Modificações