Dangling Database Cursor ('Cursor Injection')

Opis

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.

Skutki

• Confidentiality, Integrity

  Read Application Data; Modify Application Data

Zapobieganie

• Implementation

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

Słabość nadrzędna

• CWE-402 Transmission of Private Resources into a New Sphere ('Resource Leak')

Kiedy powstaje

• 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.

Dotyczy

SQL, Database Server

Źródła

1. The Oracle Hacker's Handbook — David Litchfield
2. Cursor Injection — David Litchfield