CWE-619: Dangling Database Cursor ('Cursor Injection')
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."
Last updated
Overview
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.
Background
A cursor is a feature in Oracle PL/SQL and other languages that provides a handle for executing and accessing the results of SQL queries.
Common consequences
What can happen when CWE-619 is exploited.
Read Application Data, Modify Application Data
Affects: Confidentiality, Integrity
How it happens
When it is introduced
Typically introduced during these phases of the software lifecycle.
Applies to
Languages
Technologies
How to prevent it
Practical mitigations for CWE-619, grouped by where in the lifecycle they apply.
Close cursors immediately after access to them is complete. Ensure that you close cursors if exceptions occur.
Terminology & mappings
Mapped taxonomies
- Software Fault Patterns: Tainted input to command (SFP24)
Frequently asked questions
Common questions about CWE-619.
- What is CWE-619?
- 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."
- How do you prevent CWE-619?
- Close cursors immediately after access to them is complete. Ensure that you close cursors if exceptions occur.
- What are the consequences of CWE-619?
- Exploiting CWE-619 can lead to: Read Application Data, Modify Application Data.
References
- MITRE CWE definition (CWE-619) (opens in a new tab)
- CWE-619 vulnerabilities on NVD (opens in a new tab)
- Learn: What is a CWE?
Weakness data is sourced from the MITRE CWE catalog (v4.20). CVE associations are aggregated and kept current by RadicalNotion.AI.
Stay ahead of CWE-619
Get alerted the moment a new CWE-619 vulnerability affects your stack, with AI-written analysis, severity context, and remediation guidance.