CWE-619 Dangling Database Cursor

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

• Confidentiality, Integrity: Read Application Data, Modify Application Data — The cursor could become accessible to other users while retaining the same privileges that were originally assigned. The impact of the issue depends on the cursor's role, but SQL injection attacks are commonly possible.

• [Implementation] Close cursors immediately after access to them is complete. Ensure that you close cursors if exceptions occur.

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