|
|
Status: Incomplete Weakness ID: 619 (Weakness Base)Description Summary 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." Extended Description 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. Potential Mitigations Close cursors immediately after access to them is complete. Ensure that you close cursors if exceptions occur. Other Notes The weakness can occur both as Primary and Resultant. 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. 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. References David Litchfield. "The Oracle Hacker's Handbook". David Litchfield. "Cursor Injection". <http:/ Relationships
Applicable Platforms Languages SQL Time of Introduction  ImplementationContent History Modifications Eric Dalci. Cigital. 2008-07-01. (External) updated Time_of_Introduction CWE Content Team. MITRE. 2008-09-08. (Internal) updated Relationships, Other_Notes CWE Content Team. MITRE. 2008-10-14. (Internal) updated Background_Details, Description, Relationships Previous Entry Names Dangling Database Cursor (Cursor Injection) (changed 2008-04-11) |
|
|
|||
