BaseIncompleteCWE-619

CWE-619: 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.

Abstraction: BaseA weakness specific enough to point to detection and prevention methods.
Likelihood of exploit: Not rated by MITRE
Status: Incomplete

Common consequences

ConfidentialityIntegrity
Read Application Data; Modify Application Data

Potential mitigations

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

Related weaknesses

Parent weaknesses

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

CAPEC attack patterns that exploit it

CWE 4.20 links no CAPEC attack pattern to this weakness.

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.