Dangling Database Cursor ('Cursor Injection')
Incomplete Base
Structure: Simple
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 1
Scope: ConfidentialityIntegrity
Impact: Read Application DataModify Application Data
Potential Mitigations 1
Phase: Implementation
Close cursors immediately after access to them is complete. Ensure that you close cursors if exceptions occur.
References 2
The Oracle Hacker's Handbook
David Litchfield
ID: REF-505
Cursor Injection
David Litchfield
ID: REF-506
Applicable Platforms
Languages:
SQL : Undetermined
Technologies:
Database Server : Undetermined
Modes of Introduction
Implementation
Related Weaknesses
Taxonomy Mapping
- Software Fault Patterns