Detalle CWE-619

The product does not close a database cursor properly, leaving the cursor "dangling."

Detalles de contexto

Modos de introducción

Implementation : This issue is currently reported for unhandled exceptions, but it is theoretically possible any time the programmer does not close the cursor at the proper time.

Plataformas aplicables

Lenguaje

Nombre: SQL (Undetermined)

Tecnologías

Nombre: Database Server (Undetermined)

Consecuencias comunes

Mitigaciones potenciales

Phases : Implementation
Close cursors immediately after access to them is complete. Ensure that you close cursors if exceptions occur.

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.)

Notas de mapeo de vulnerabilidades

Justificación : This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Comentario : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.

Referencias

REF-505

The Oracle Hacker's Handbook
David Litchfield.

REF-506

Cursor Injection
David Litchfield.
http://www.davidlitchfield.com/cursor-injection.pdf

Envío

Modificaciones