CWE-619—Dangling Database Cursor ('Cursor Injection')

Weakness Name

Dangling Database Cursor ('Cursor Injection')

Description

If a database cursor is not closed properly, then it could become accessible to other users while retaining the same privileges that were originally assigned, leaving the cursor "dangling."

For example, an improper dangling cursor could arise from unhandled exceptions. The impact of the issue depends on the cursor's role, but SQL injection attacks are commonly possible.

Common Consequences

Scope:

Confidentiality, Integrity

Impact:

Read Application Data, Modify Application Data

Related Weaknesses

• CWE-402Transmission of Private Resources into a New Sphere ('Resource Leak')