Detalle CWE-1121

The code contains McCabe cyclomatic complexity that exceeds a desirable maximum.

Modos de introducción

Implementation

Plataformas aplicables

Lenguaje

Class: Not Language-Specific (Undetermined)

Consecuencias comunes

Métodos de detección

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.)
Efectividad : High

Notas de mapeo de vulnerabilidades

Justificación : This entry is primarily a quality issue with no direct security implications.
Comentario : Look for weaknesses that are focused specifically on insecure behaviors that have more direct security implications.

Referencias

REF-963

Providing a Framework for Effective Software Quality Assessment
Robert A. Martin, Lawrence H. Shafer.
https://www.researchgate.net/publication/285403022_PROVIDING_A_FRAMEWORK_FOR_EFFECTIVE_SOFTWARE_QUALITY_MEASUREMENT_MAKING_A_SCIENCE_OF_RISK_ASSESSMENT

REF-964

Cyclomatic Complexity
Wikipedia.
https://en.wikipedia.org/wiki/Cyclomatic_complexity

REF-960

Automated Source Code Maintainability Measure (ASCMM)
Object Management Group (OMG).
https://www.omg.org/spec/ASCMM/

Envío

Modificaciones