CWE-619 — Dangling Database Cursor ('Cursor Injection')
CWE-619: Dangling Database Cursor ('Cursor Injection')
MITRE CWE weakness
| Kind | Weakness |
| Abstraction | Base |
| Status | Incomplete |
| Likelihood of exploit | — |
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
- Confidentiality, Integrity: Read Application Data, Modify Application Data
Mitigations
Implementation — Close cursors immediately after access to them is complete. Ensure that you close cursors if exceptions occur.
References
- CWE page: https://cwe.mitre.org/data/definitions/619.html
- CWE list: https://cwe.mitre.org/data/index.html