CWE-619 Base Incomplete

Dangling Database Cursor ('Cursor Injection')

A dangling database cursor occurs when a database cursor is not properly closed, potentially allowing other users to access it while it retains its original, often elevated, privileges.

Definition

What is CWE-619?

A dangling database cursor occurs when a database cursor is not properly closed, potentially allowing other users to access it while it retains its original, often elevated, privileges.
This vulnerability typically surfaces when errors or exceptions in an application are not handled correctly, leaving the cursor open. For instance, if a function that opens a cursor throws an unhandled exception before reaching the code that closes it, the cursor remains active and 'dangles' in the database. The primary risk is that this open cursor can be exploited, often leading to SQL injection attacks. The severity depends on what the cursor was designed to do, but since it still holds its initial permissions, an attacker could potentially use it to execute unauthorized database operations or access sensitive data.
Real-world impact

Real-world CVEs caused by CWE-619

No public CVE references are linked to this CWE in MITRE's catalog yet.

How attackers exploit it

Step-by-step attacker path

  1. 1

    Identify a code path that handles untrusted input without validation.

  2. 2

    Craft a payload that exercises the unsafe behavior — injection, traversal, overflow, or logic abuse.

  3. 3

    Deliver the payload through a normal request and observe the application's reaction.

  4. 4

    Iterate until the response leaks data, executes attacker code, or escalates privileges.

Vulnerable code example

Vulnerable pseudo

MITRE has not published a code example for this CWE. The pattern below is illustrative — see Resources for canonical references.

Vulnerable pseudo 
// Example pattern — see MITRE for the canonical references.
function handleRequest(input) {
  // Untrusted input flows directly into the sensitive sink.
  return executeUnsafe(input);
}
Secure code example

Secure pseudo

Secure pseudo 
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
  const safe = validateAndEscape(input);
  return executeWithGuards(safe);
}
What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Prevention checklist

How to prevent CWE-619

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

How to detect CWE-619

SAST High

Run static analysis (SAST) on the codebase looking for the unsafe pattern in the data flow.

DAST Moderate

Run dynamic application security testing against the live endpoint.

Runtime Moderate

Watch runtime logs for unusual exception traces, malformed input, or authorization bypass attempts.

Code review Moderate

Code review: flag any new code that handles input from this surface without using the validated framework helpers.

Plexicus auto-fix

Plexicus auto-detects CWE-619 and opens a fix PR in under 60 seconds.

Codex Remedium scans every commit, identifies this exact weakness, and ships a reviewer-ready pull request with the patch. No tickets. No hand-offs.

Get a demo Try Plexicus free
Frequently asked questions

Frequently asked questions

What is CWE-619?

A dangling database cursor occurs when a database cursor is not properly closed, potentially allowing other users to access it while it retains its original, often elevated, privileges.

How serious is CWE-619?

MITRE has not published a likelihood-of-exploit rating for this weakness. Treat it as medium-impact until your threat model proves otherwise.

What languages or platforms are affected by CWE-619?

MITRE lists the following affected platforms: SQL, Database Server.

How can I prevent CWE-619?

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

How does Plexicus detect and fix CWE-619?

Plexicus's SAST engine matches the data-flow signature for CWE-619 on every commit. When a match is found, our Codex Remedium agent opens a fix PR with the corrected code, tests, and a one-line summary for the reviewer.

Where can I learn more about CWE-619?

MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/619.html. You can also reference OWASP and NIST documentation for adjacent guidance.

Related weaknesses

Weaknesses related to CWE-619

CWE-402 Parent

Transmission of Private Resources into a New Sphere ('Resource Leak')

This vulnerability occurs when an application unintentionally exposes internal resources, like files, memory, or database connections, to…

CWE-403 Sibling

Exposure of File Descriptor to Unintended Control Sphere ('File Descriptor Leak')

This vulnerability occurs when a parent process launches a child process without first closing sensitive file descriptors. The child…

Resources

Further reading

Ready when you are

Don't Let Security
Weigh You Down.

Stop choosing between AI velocity and security debt. Plexicus is the only platform that runs Vibe Coding Security and ASPM in parallel — one workflow, every codebase.

Get started free Book a demo