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.

Background Details

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.

Modes Of Introduction

Implementation : This issue is currently reported for unhandled exceptions, but it is theoretically possible any time the programmer does not close the cursor at the proper time.

Applicable Platforms

Language

Name: SQL (Undetermined)

Common Consequences

Potential Mitigations

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

Vulnerability Mapping Notes

Rationale : This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Comments : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.

References

REF-505

The Oracle Hacker's Handbook
David Litchfield.

REF-506

Cursor Injection
David Litchfield.
http://www.davidlitchfield.com/cursor-injection.pdf

Submission

Modifications