BaseIncomplete

CWE-619Dangling Database Cursor ('Cursor Injection')

Category: injection

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

  • Confidentiality / Integrity — Read Application Data, Modify Application Data

Potential mitigations· 1

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

References

  1. https://cwe.mitre.org/data/definitions/619.html

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CVE
CVE-2025-62354
CWE
SQL Injection: Hibernate
CWE
Uncaught Exception
CWE
Improper Neutralization of Quoting Syntax
CVE
CVE-2025-23176
CWE
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.